Binutils pass 2

Ken Moffat ken at
Sun Jan 25 04:22:11 PST 2004

On Sun, 25 Jan 2004, John Paul wrote:

> Hello everybody,
> I've this message during the "make check" for binutils pass 2. I've look
> on the web, for an help but I didn't find any answer to my question.
> What could be wrong ?

 It is covered in, but it's a bit hard to

> I'm using a Suse 8.2 wih gcc 3.3.2   (also build for my LFS).
> /bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2  -o -rpath /tools/lib -release 2.14  archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo opncls.lo reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo simple.lo archive64.lo `cat ofiles` -L../libiberty/pic -liberty
> ./libtool: line 1: cd: ../libiberty/pic: No such file or directory
> libtool: link: cannot determine absolute directory name of `../libiberty/pic'
> make[3]: *** [] Error 1
> make[3]: Leaving directory `/media/lfs/sources/binutils-build/bfd'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/media/lfs/sources/binutils-build/bfd'
> make[1]: *** [all-recursive-am] Error 2
> make[1]: Leaving directory `/media/lfs/sources/binutils-build/bfd'
> make: *** [all-bfd] Error 2
> Thanks for your help.
> John

 The suggestion is that you didn't delete the directories (source and
build) from pass 1.  You should have removed these during "locking in

This is a job for Riviera Kid!

More information about the lfs-support mailing list