>>> are overwritten. So I guess there is nothing wrong with the binaries. >>> What is wrong is with the libraries, like libanl, which are part of >>> glibc (and others, which are built later). So I guess something went >>> wrong during glibc build. >>> One possibility is that '/bin/dash' is used instead of '/bin/bash'. >>> Have you checked the link /bin/sh->/bin/bash? >>> Another possibility is a typo in the configure line, or that >>> $LFS_TGT was wrongly set at that point, or... >>> >>> Pierre >> >> It should be that /bin/bash, not /bin/dash is the active shell. >> >> >> >Sorry if it was not clear: /bin/sh should be a symbolic link to >/bin/bash, not /bin/dash. If you use a debian-like system, the default >is to point to /bin/dash, and that causes issues (I am not able to find >a thread ATM).
No, this is definitely not the cause of the problem. /bin/sh was properly linked all through out the build. Typo in the configuration line is also out of the question. I cut and paste commands from the book. So if there is a type it is in the book. Any other suggestions? Is it time to just place this build on the scrap heap and start again from scratch? If so, what should I look out for on the next build to make sure I don't run into the same kind of problem again? Daer Samej -- 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
