On Sat, Oct 16, 2010 at 07:35:55PM +0530, sreejan kumar wrote: > Hello > I have been facing some problem in running this command > could you specify how should i proceed?? > > > r...@trinity-desktop:/# 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 > > /tools/bin/env: /tools/bin/bash: No such file or directory > > r...@trinity-desktop:/#
Please see http://www.linuxfromscratch.org/lfs/faq.html#any-no-such-file What seems to have happened is that some, or all, of the programs in /tools are linked to /usr/lib on the host system. Sometimes this has happened when people resumed a build during chapter 5 and forgot to get their environment correct. To confirm that diagnosis, from the host system run ldd /tools/bin/bash - any references to files in /usr/lib are the problem. If this isn't a general problem (i.e. you built and adjusted the toolchain correctly), the way to diagnose the extent of the problem is to pick a program [ not a script ] or library installed by each package after glibc [ see chapter 6 for what gets installed ] and run ldd against it. Where only one or two packages are wrong, it is fixable (make sure the environment is correct, then rebuild those packages). If everything is wrong, you failed to adjust the toolchain correctly. In that case, best to delete the contents of /tools and start again. The tests to see if the toolchain was adjusted correctly *usually* catch problems. Alternatively, you might have failed to install /tools/bin/env (coreutils). ĸ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
