On 3/22/06, Richard Melville <richard at netvaluesystems.com
<http://linuxfromscratch.org/mailman/listinfo/lfs-support>> wrote:
/
/>/ The sanity check fails, as does gcc -dumpmachine. However, if I exit
/>/ the chroot environment and run the sanity check again, all is well. The
/>/ sanity check returns /tools/lib/ld-linux.so.2 and gcc -dumpmachine
/>/ returns i686-pc-linux-gnu.
/
First, what's the exact error give when you attempt the sanity check
in the chroot?
Second, are you sure you have all the proper symlinks in place from
Creating Essential Symlinks?
Third, let's try a souped up sanity check similar to the one in the SVN book.
http://www.linuxfromscratch.org/lfs/view/development/chapter06/readjusting.html
echo 'main(){}' > dummy.c
cc dummy.c -Wl,--verbose &> dummy.log
readelf -l a.out | grep 'ld-linux'
grep 'libc.so.6' dummy.log
grep 'SEARCH_DIR' dummy.log
grep 'crt[1in].*succeeded' dummy.log
grep 'found' dummy.log
That should help get to the bottom of this mess.
--
Dan
Hi Dan
In the chroot environment I can't even get past compiling dummy.c;
*cc dummy.c* returns the reply */tools/bin/cc: No such file or directory*
I've checked all the symlinks and they are installed.
Ken
The libraries all seem to be in place. I understand what you are saying
about being linked to a library on the host which disappears after entering
then chroot environment. I though that the sanity check was meant to guard
against this. How can I check whether this is the case?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
