Problems cross compiling xfsprogs
A message that is not in the archive (sent off-list or not yet received): 20060720114406.0fdf557a@XEONBOX
Quoted 6 lines · Jackson Jones
[email protected], Nathan,
Hi, my name is Jackson Jones, I am working on an embedded linux project. We are using XFS for our filesystem. I am updating our toolchain to a 2.6.12 kernel (from a 2.4.25).
Quoted 7 lines
We were using xfsprogs-2.6.25 (which did fine against the 2.4.25 kernel. When compiling against the 2.6.12 kernel, I got the following error(the entire build log is attached)
....
fadvise.o: In function `fadvise_f':/home/jjones/depot/mp/exp-perf/output/mipsel/build/debug/xfsprogs/io/fadvise.c:122:
undefined reference to `posix_fadvise64'
This sounds like you have an ancient libc... is that possible?
Quoted 5 lines
I moved up to xfsprogs-2.7.11 and got (entire log is attached). -DPACKAGE=\"xfsprogs\" -I../include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 --tag=gcc -c
bit.clibtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag' gmake[2]: *** [bit.lo] Error 1 make[1]: *** [default] Error 2 make[1]: Leaving directory
Urgh, I have no idea - libtool Just Works (TM) for me, so I don't mess with it... if you need to pass more options in, bounce us a patch implementing that I guess.
Quoted 2 lines
Is there a version (of xfsprogs, which you recommend, or where in the build script should I insert the --tag=gcc option after the mode=compile? I am
Dunno.
Quoted 2 lines
guessing the libtool is confused since our compiler is called mipsel-linux-gcc.
Did setting CC in the environment before running configure have any effect? (not sure, I've not done it, but maybe..)
cheers.
Signature · 1 line
Nathan