My first thought is that the symbolic link for the tools directory from
chapter 4.2 isn't properly set up. Once you "chroot", anything outside
of what will be your new directory structure shouldn't exist. So if
that symlink doesn't point to the correct place, gcc might not be found.
I don't have an active build to compare it to, so I hope I give you
correct information. Maybe from the host, outside of chroot, you could
make sure that your $LFS partition is mounted and:
ls /tools
Then unmount the $LFS partition and run the same command again. While
mounted, it should list everything you've built in the toolchain. While
unmounted it should list nothing or maybe even return an error. If the
above lists the same contents both times, your symlink from 4.2 was
probably wrong and your /tools directory is on the host partition
instead of the $LFS partition.
If that isn't what's wrong, I'm afraid you will probably have to wait
for someone else more knowledgeable than me to help you. Also if I have
given you false information, I do hope someone corrects me.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
