x86_64-64 10.5 Binutils make check problem

Ken Moffat ken at linuxfromscratch.org
Mon Nov 14 07:13:16 PST 2005


On Mon, 14 Nov 2005, Klaus Dimde wrote:

> Hi there,
>
> once again I'm doing it the lfs way with my X86_64-Machine and use the
> No-multilib-version of the clfs book. When doing the make check in Chapter
> 10.5 Binutils the ld-bootstrap tests fail. The concerning part in ld/ld.log
> is:
> Running /sources/binutils-2.16.1/ld/testsuite/ld-bootstrap/bootstrap.exp ...
> /sources/binutils-build/ld/ld-new -m elf_x86_64 -o tmpdir/ld-partial.o -r
> 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_x86_64.o eelf_i386.o
> ei386linux.o
> /sources/binutils-build/ld/ld-new -m elf_x86_64  -o tmpdir/ld1
> -dynamic-linker /lib64/ld-linux-x86-64.so.2 /usr/lib/crt1.o /usr/lib/crti.o /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/crtbegin.o
> tmpdir/ld-partial.o ../bfd/.libs/libbfd.a ../libiberty/libiberty.a
> -L/usr/lib
> --start-group /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/libgcc.a /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/libgcc_eh.a
> -lc
> --end-group /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/crtend.o /usr/lib/crtn.o
> tmpdir/ld1 -m elf_x86_64  -o tmpdir/ld2
> -dynamic-linker /lib64/ld-linux-x86-64.so.2 /usr/lib/crt1.o /usr/lib/crti.o /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/crtbegin.o
> 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_x86_64.o eelf_i386.o
> ei386linux.o  ../bfd/.libs/libbfd.a ../libiberty/libiberty.a   -L/usr/lib
> --start-group /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/libgcc.a /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/libgcc_eh.a
> -lc
> --end-group /tools/lib/gcc/x86_64-unknown-linux-gnu/4.0.2/crtend.o /usr/lib/crtn.o
> couldn't execute "tmpdir/ld1": no such file or directory
> FAIL: bootstrap
>
> So for any reason the test-suite searches for ld-linux-x86-64.so.2 in /lib64
> wich doesn't exist. Symlinking the directory solves the problem, but my
> question is, may this be any error done by myself? I was quite happy to get
> rid of the lib64 directory-stuff...
>

Wow, thanks for the pointer to ld.log, I'd missed that when trying to 
work out what was going wrong.  In my experience, ld *always* fails some 
tests on x86_64-64 (5 in bootstrap, and a couple elsewhere, maybe cd) - 
looks like you've solved this.

  I'm sure a symlink is an adequate (if messy) workaround to this 
problem, I'll add it to the book.  Cheers!

Ken
-- 
  das eine Mal als Tragödie, das andere Mal als Farce


More information about the cross-lfs mailing list