On 3/13/07, Matthew Burgess <[EMAIL PROTECTED]> wrote:
On Monday 12 March 2007 19:44, Dan Nicholson wrote:
> So, I'm proposing that we force
> /bin/bash as the shebang for ldd. Two possible ways are:
>
> 1. Prior to configure and changing dirs - sed -i 's|@BASH@|/bin/bash|'
> elf/ldd.in
I like this option too. It's easy to explain exactly what that command does
and ensure its effects are limited to just `ldd'.
Suggestions on the explanation welcomed for this patch.
--
Dan
Index: BOOK/chapter06/glibc.xml
===================================================================
--- BOOK/chapter06/glibc.xml (revision 7962)
+++ BOOK/chapter06/glibc.xml (working copy)
@@ -87,6 +87,14 @@
<screen><userinput>patch -Np1 -i ../&glibc-branch_update-patch;</userinput></screen>
+ <para>The <command>ldd</command> utility installed by Glibc is a Bash
+ script that will inadvertantly call <command>/bin/sh</command> as its
+ interpreter. This can be a problem if a different shell is installed later
+ as <command>/bin/sh</command>. Force <command>bash</command> to be used
+ with the following substitution:</para>
+
+<screen><userinput>sed -i 's|@BASH@|/bin/bash|' elf/ldd.bash.in</userinput></screen>
+
<para>The Glibc documentation recommends building Glibc outside of the source
directory in a dedicated build directory:</para>
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
