----- Original Message ----- From: "Joe" <[EMAIL PROTECTED]> To: "LFS Developers Mailinglist" <lfs-dev@linuxfromscratch.org> Sent: Saturday, April 05, 2008 4:59 AM Subject: Re: SVN-20080403 : 5.6.1. Installation of Glibc failure
... > Well, according to this > (https://launchpad.net/ubuntu/+spec/dash-as-bin-sh), /bin/sh in Ubuntu > edgy is symlinked to dash instead of bash, so even though > > |bash --version | head -n1 | cut -d" " -f2-4 > | > |may indicate that a user has bash newer than 2.05a, any build shell > scripts that start with #!/bin/sh may or may not behave as expected (I > have no practical experience with dash but I read that it has caused > problems in places). If this is indeed a potential problem, perhaps the > second sentence could be rephrased along these lines:| > ||| > | This should not be an issue for most modern Linux distributions, but > be aware that some commonly used programs, such as /bin/sh, may be > symlinked to a different program. > > The only such programs that come to mind are sh, make and awk (cc could > also be a problem but very unlikely under Linux). > > The alternative, which I think is a cleaner bootstrapping procedure, is > to change the order so that bash gets built first and symlinked the way > we want it and GNU make second (which is the way DIY does it). The > downside is that it does require second passes during Chapter 5. > only glibc has dash|bash trouble, so specifically calling /bin/bash could be an acceptable workaround. This should work on ubuntu (still in my to-do list to test that) CONFIG_SHELL=/bin/bash ../glibc-2.7/configure Gilles -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
