[uClibc]Linking error under 0.9.10

dysan2k at linuxanthology.org dysan2k at linuxanthology.org
Thu Apr 4 09:27:38 UTC 2002


Here's a problem that I've run into that may make more sense to you all than
myself.  I've compiled a LFS system with binutils-2.11.2, gcc-2.95.3, and
kernel-2.4.18.  I go to compile the 0.9.10 version of uClibc under this system
and end with:

LIBRARY_CACHE disabled -- not building ldconfig
../../extra/gcc-uClibc/i386-uclibc-gcc -Wall -Os  -march=i386
-mpreferred-stack-boundary=2 -malign-functions=0 -malign-jumps=0 -malign-loops=0
-fno-builtin -nostdinc -pipe -nostdinc -I../../include
-I/usr/lib/gcc-lib/i386-linux/2.95.4/include -I. -D_LIBC  -DNDEBUG  -fPIC
-D_LIBC_REENTRANT -static --uclibc-use-build-dir -s -DUCLIBC_TARGET_PREFIX=\"/\" \
	-DUCLIBC_DEVEL_PREFIX=\"/usr/i386-linux-uclibc\" \
	-DUCLIBC_BUILD_DIR=\"/lfs/build/uClibc\" \
	-DUCLIBC_LDSO=\"ld-uClibc.so.0\" \
	ldd.c -o ldd.target
make[2]: *** [ldd.target] Error 255
make[2]: Leaving directory `/lfs/build/uClibc/ldso/util'

I've tried untarring and trying from scratch, and pulling down CVS.  Both
systems cause the exact same issue, and the cc/gcc wrappers don't work as a
result when I install.  I did a 'make clean' on the directories, along with a
new untar, and tried it on my debian-unstable (gcc 2.95.4, binutils-2.11.2,
kernel 2.4.17) and the uClibc runs fine.  I decided that it could be the
compiler, and tried compiling gcc 3.0.4 under the LFS setup.  Once again, exact
same error.  I'm not quite sure where to run now.  I've read the past 3 months
of mailing list archives, found only one item similar in 0.9.9, but didn't quite
understand the fix for it.  I'm currently building a gcc 3.0.4 static install
for the LFS system off my debian one, so I'm hoping that this may solve the problem?

Any suggestions?

Ed Stafford



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



More information about the uClibc mailing list