Error ater glibc config in chap6

Henry K van Eyken vaneyken at sympatico.ca
Mon Feb 9 21:13:36 PST 2004


On Tue, 2004-01-27 at 18:54, Bertjan Broeksema wrote:
> Hi all,
> 
> 
> I'm using lfs 5.0. I followed all steps, and everything went ok, but after
> re-adjusting the toolchain there is a litle test.
> 
> echo 'main(){}' > dummy.c
> gcc dummy.c
> readelf -l a.out | grep ': /lib'
> 
> When i run this test i get this error:
> 
> /tools/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/../../../../i686-pc-linux-gnu/bin
> /ld: error while loading shared libraries: libbfd-2.14.so: cannot open
> shared object file: No such file or directory
> collect2: ld returned 127 exit status
> 
> I think it has something to do with binutils, but don't know what to do now.
> Can somebody give me a hint?
> 
> Grtz,
> 
> Bertjan

Bertjan.

If it is any consolation, I have a similar problem and ran into
it twice. 

The command gcc dummy.c produces this message:
/tools/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/../../../../i686-pc-linux-gnu/bin/ld: 
warning: ld-linux.so.2, needed by /tools/lib/libc.so.6, not found 
(try using -rpath or -rpath-link) etc, etc.

Fact is that there is no such a long string of subdirectories. Hence, 
the message is wrong.

I did not have this problem during my first LFS run, which I did with
the same software on a 450-MHz Pentium III machine. Now I am using a
fast Athlon 2600+. Checked the "Target triplet" and the name of the
dynamic linker (ref. "Toolchain Technical Notes").

I have eliminated the "specs" file as a source of error 

Have you found a solution? What CPU do you have?

Henry

-- 
Henry K van Eyken <vaneyken at sympatico.ca>




More information about the lfs-support mailing list