ok guys Im on 6.3. Entering the Chroot Environment.

My bash prompt is focused on /mnt/lfs....

When I put in the command:


chroot "$LFS" /tools/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h

..as is specified in the beginning of this chapter to enter the chroot enviroment I get this error message:

/tools/bin/bash: error while loading shared libraries: libtermcap.so.2: cannot open shared object file: No such file or directory

Is this a good thing? Is this a bad thing? .....help please! You guys are the masters

It looks like you didn't set up the environment properly and compiled the things in /tools linked against the libraries on your host system. libtermcap.so.2 is not part of the temporary tools, in fact I don't have it on my system at all.
Try again and this time pay attention to the steps involved in creating and becoming the user lfs

Thanks Andrew, but I got it. Just in case anyone else has this problem, here is how you fix it....

While compiling bash in chapter 5, the lfs authors obviously left out something of great importance within the configure stage. You must configure bash with a static link and prefix tools with ncurses, or you aaint gonna go any furthure at this stage in the process. Im not sure if it was done as a typo or if the authors left it out on purpose to get you to think, but Ill bet it was the later.

At any rate, go back and recompile bash using this configure command instead of the one found in chapter 5:

./configure --enable-static-link --prefix=/tools --with-curses --without-bash-malloc

then you will get the output "i have no name!" when you enter the chroot commands given in chapter 6.

Its a simple matter of one linked library not being there! Good one lfs!.....lol, you almost had me on that one