This is just a preliminary advice, particularly for Bruce (at the moment, I can't reach the lfs website to raise a ticket). On clfs, we're gradually getting thorough failures in the testsuites as we head for our first release. One of these (the c++-types-check.out failure in glibc-2.4) appears to be caused by su'ing to another user to build the temporary system.
Greg has provided a pointer to the bug report for bash, http://lists.gnu.org/archive/html/bug-bash/2006-05/msg00018.html I can see the symptoms in my last LFS build log for bash (in March) checking whether /dev/fd is available... absent [ in a good build, this will report 'standard' ] but I don't have the glibc test results, so I don't know for sure if the error manifests itself with glibc-2.3.6. Hopefully, somebody has test results ? For clfs, we are likely to load config.cache (when we configure bash) with bash_cv_dev_fd=standard, but Dan's suggestion of sed -i '[EMAIL PROTECTED] \(/dev/fd/.\)@-e \1@' configure might be more appropriate for LFS. At the moment, neither of these proposed fixes has been tested. Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
