On Sun, 2013-07-28 at 17:58 +0100, Unix User wrote: > Dear list, > Hello,
> > after my last question everything in chapter 5 went fine - now I stuck > again... > > > In chapter 6.7.1 (Linux api headers): > > -----------------8<------------------- > root:/sources/linux-3.10.2# make mrproper > make: gcc: Command not found > -----------------8<------------------- > > PATH in chroot is: /bin:/usr/bin:/sbin:/usr/sbin:/tools/bin > > ldd gcc/g++/cc shows: > -----------------8<------------------- > root:/sources/linux-3.10.2# ldd -v /tools/bin/gcc > /tools/bin/ldd: line 116: /tools/bin/gcc: No such file or directory > root:/sources/linux-3.10.2# ldd -v /tools/bin/g++ > /tools/bin/ldd: line 116: /tools/bin/g++: No such file or directory > root:/sources/linux-3.10.2# ldd -v /tools/bin/cc > /tools/bin/ldd: line 116: /tools/bin/cc: No such file or directory This is a slightly ambiguous error from `ldd'. It means `/lib64/ld-linux-x86-64.so.2' cannot be found (which you can see below) as it is not present in the chroot environment. It doesn't mean the binary isn't there. That caught me out when I first saw it too. > BUT: > root:/sources/linux-3.10.2# ldd /tools/bin/bash > linux-vdso.so.1 (0x00007fff52b05000) > libncurses.so.5 => /tools/lib/libncurses.so.5 (0x00007f793d896000) > libdl.so.2 => /tools/lib/libdl.so.2 (0x00007f793d692000) > libgcc_s.so.1 => /tools/lib/libgcc_s.so.1 (0x00007f793d47d000) > libc.so.6 => /tools/lib/libc.so.6 (0x00007f793d0cf000) > /tools/lib64/ld-linux-x86-64.so.2 (0x00007f793dae5000) > -----------------8<------------------- > > Interestingly, the corresponding binary is present: > -----------------8<------------------- > root:/sources/linux-3.10.2# ls -la /tools/bin/gcc > -rwxr-xr-x 3 root root 558384 Jul 25 22:24 /tools/bin/gcc > root:/sources/linux-3.10.2# ls -la /tools/bin/g++ > -rwxr-xr-x 4 root root 562480 Jul 25 22:24 /tools/bin/g++ > root:/sources/linux-3.10.2# ls -la /tools/bin/cc > lrwxrwxrwx 1 root root 3 Jul 25 19:53 /tools/bin/cc -> gcc > -----------------8<------------------- > > As it seems, except bash, gcc and g++ and cc are linked to the host (right?), > since outside chroot: > -----------------8<------------------- > lfs@venus:/media/lfs/e32e48f2-ea36-4622-89e5-19e22084a06e$ ldd > $LFS/tools/bin/gcc > linux-vdso.so.1 => (0x00007fff5d1fe000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa605d0a000) > /lib64/ld-linux-x86-64.so.2 (0x00007fa6060d2000) > lfs@venus:/media/lfs/e32e48f2-ea36-4622-89e5-19e22084a06e$ ldd > $LFS/tools/bin/g++ > linux-vdso.so.1 => (0x00007ffff7355000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd9a5e36000) > /lib64/ld-linux-x86-64.so.2 (0x00007fd9a61fe000) > lfs@venus:/media/lfs/e32e48f2-ea36-4622-89e5-19e22084a06e$ ldd > $LFS/tools/bin/cc > linux-vdso.so.1 => (0x00007fffb97fe000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5196e2b000) > /lib64/ld-linux-x86-64.so.2 (0x00007f51971f3000) > lfs@venus:/media/lfs/e32e48f2-ea36-4622-89e5-19e22084a06e$ ldd > $LFS/tools/bin/bash > linux-vdso.so.1 (0x00007fff40dd1000) > libncurses.so.5 => /tools/lib/libncurses.so.5 (0x00007fc3ea680000) > libdl.so.2 => /tools/lib/libdl.so.2 (0x00007fc3ea47c000) > libgcc_s.so.1 => /tools/lib/libgcc_s.so.1 (0x00007fc3ea267000) > libc.so.6 => /tools/lib/libc.so.6 (0x00007fc3e9eb9000) > /tools/lib64/ld-linux-x86-64.so.2 (0x00007fc3ea8cf000) > -----------------8<------------------- So looks like `bash' is linked correctly but `gcc' isn't. That seems pretty weird. > > My question now is, is there a way to fix things (I would say I have not done > a mistake but obviously something went wrong) or should I start from the > beginning to ensure integrity of the LFS system? > > Honestly I would say you're probably better starting again and making extra sure that you follow all the instructions for building `gcc'. Make sure you apply the instructions both times you build `gcc' in ch5. The compiler is a little too critical to try and fix-up later. > Thanks in advance, > Seba > Thanks, Mike -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
