[Barrelfish-users] Barrelfιsh build errors after update

[Georgios Varisteas]

Hi again,

The patch fixed that error only to stumble upon another one...

gcc -g -O2 ./x86_64/lib/crt0.o ./x86_64/lib/crtbegin.o -fno-builtin -nostdlib -Wl,-z,max-page-size=0x1000 
-Wl,--build-id=none -m64 -Xlinker --undefined=vfs_dummy -o ./x86_64/sbin/bb_floorplan 
./x86_64/usr/woolapps/_for_app_bb_floorplan/bots/floorplan/floorplan.o 
./x86_64/usr/woolapps/_for_app_bb_floorplan/bots/common/bots_main.o 
./x86_64/usr/woolapps/_for_app_bb_floorplan/bots/common/bots_common.o ./x86_64/lib/libbiasusr_root.a 
./x86_64/lib/libtimer.a ./x86_64/lib/libvfs.a ./x86_64/lib/libnfs.a ./x86_64/lib/libahci.a ./x86_64/lib/liblwip.a 
./x86_64/lib/libcontmng.a ./x86_64/lib/libprocon.a ./x86_64/lib/libposixcompat.a ./x86_64/lib/libbarrelfish.a 
./x86_64/errors/errno.o ./x86_64/lib/libnewlib.a ./x86_64/lib/crtend.o ./x86_64/lib/libcollections.a
./x86_64/lib/libvfs.a(fopen.o): In function `vfs_fopen_init':
/home/georgios/barrelfish/build/../src/lib/vfs/fopen.c:264: undefined reference to `vfsfd_lseek'
/home/georgios/barrelfish/build/../src/lib/vfs/fopen.c:264: undefined reference to `vfsfd_close'
/home/georgios/barrelfish/build/../src/lib/vfs/fopen.c:264: undefined reference to `vfsfd_write'
/home/georgios/barrelfish/build/../src/lib/vfs/fopen.c:264: undefined reference to `vfsfd_read'
/home/georgios/barrelfish/build/../src/lib/vfs/fopen.c:264: undefined reference to `vfsfd_open'
collect2: ld returned 1 exit status
make: *** [x86_64/sbin/bb_floorplan] Error 1

floorplan app uses vfs and ahci thus has all those added... Any hints for this one?

cheers,
Georgios


________________________________________
From: Kornilios Kourtis [kornilios.kourtis at inf.ethz.ch]
Sent: Tuesday, March 06, 2012 20:09
To: barrelfish-users at lists.inf.ethz.ch
Subject: Re: [Barrelfish-users] Barrelfιsh   build errors after update

Hi Georgios,

On Tue, Mar 06, 2012 at 05:16:03PM +0000, Georgios Varisteas wrote:
> I thought of posixcompat myself, this existed with oldc also and if you
> check the actuall gcc command (included in my initial email) you can
> see that it is included. Is it possible that it is a library linking
> order problem? If I'm
> not mistaken libs are linked in reverse order, right?
>
> Anyway, posixcompat is included automatically and it is not the source
> of the error.

Can you try the attached patch? I can't reproduce the problem, so I'm not
sure if it'll work. If it doesn't, can you try creating a test case that
reproduces the problem?

cheers,
Kornilios.

--
Kornilios Kourtis