binutils ld install error - ch 5 - locking in glibc

Dean Hall dean-lists at deanpence.com
Sun Apr 25 22:06:58 PDT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On <chapter05/lockingglibc.html>, I'm running `make -C ld install`, and I
get the following output, which includes a linker error:

lfs at new:binutils-build> make -C ld install
make: Entering directory `/mnt/lfs/sources/binutils-build/ld'
Making install in po
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/ld/po'
make[1]: Nothing to be done for `install'.
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/ld/po'
make[1]: Entering directory `/mnt/lfs/sources/binutils-build/ld'
/bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes
- -Wmissing-prototypes -g -O2  -o ld-new  ldgram.o ldlex.o lexsup.o ldlang.o
mri.o ldctor.o ldmain.o ldwrite.o ldexp.o ldemul.o ldver.o ldmisc.o
ldfile.o ldcref.o eelf_i386.o
ei386linux.o  ../bfd/libbfd.la ../libiberty/libiberty.a
gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -o ld-new
ldgram.o ldlex.o lexsup.o ldlang.o mri.o ldctor.o ldmain.o ldwrite.o
ldexp.o ldemul.o ldver.o ldmisc.o ldfile.o ldcref.o eelf_i386.o
ei386linux.o  ../bfd/.libs/libbfd.a ../libiberty/libiberty.a
../libiberty/libiberty.a(cp-demangle.o)(.text+0xd4e): In function
`demangle_identifier':
/mnt/lfs/sources/binutils-build/libiberty/../../
binutils-2.14/libiberty/cp-demangle.c:1489: undefined reference to
`__ctype_b'
collect2: ld returned 1 exit status
make[1]: *** [ld-new] Error 1
make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/ld'
make: *** [install-recursive] Error 1
make: Leaving directory `/mnt/lfs/sources/binutils-build/ld'

I'm using LFS 5.0 stable on a Debian 3 system:

root at new:root> gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
root at new:root> uname -a
Linux new 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown

I installed LFS successfully with a SuSE 9.0 host distro previously (on
another machine) and completely successfully; could this be something
Debian-specific? Is this a known issue? Any other thoughts on the cause and
solution?


Regards,
Dean
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAjJj4Bnn70KGO4CURAhvUAJ4ykxFEHMVPupg1/ebzU1ed/z6tdwCeKaU+
Vl4lCsA6YjaD7buigM+D+sI=
=qOx8
-----END PGP SIGNATURE-----



More information about the lfs-support mailing list