On Wed, Oct 27, 2010 at 05:46:42PM +0100, David Shaw wrote: > > Both the above commands were executed within the chroot. Interestingly > (to me, at least, but then I'm no expert), checking the file from > outside the chroot: > > da...@david-laptop-home:~$ ldd /mnt/lfs/tools/bin/gcc > linux-gate.so.1 => (0x00ea6000) > libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x00443000) > /lib/ld-linux.so.2 (0x008d5000) > > da...@david-laptop-home:/mnt/lfs/tools/bin$ ./gcc > gcc: no input files > > So gcc is there and appears to be working. What gives? > > David Shaw > 1. It's finding the host libc - once you are in chroot you don't have any access to that. Sounds as if you went wrong in 'adjusting the toolchain'.
2. Not necessarily relevant to this problem, but that bizzare path to libc.so.6 (I was expecting /lib/libc.so.6 instead of the correct /tools/lib version) sounds like debian ? If so, please check the 'host requirements', particularly awk and /bin/sh. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
