Ver Fonte

Force ldd to use /bin/bash as it's Bash-specific

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7973 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Dan Nichilson há 18 anos atrás
pai
commit
a4cb337400
2 ficheiros alterados com 13 adições e 0 exclusões
  1. 5 0
      chapter01/changelog.xml
  2. 8 0
      chapter06/glibc.xml

+ 5 - 0
chapter01/changelog.xml

@@ -39,6 +39,11 @@
     <listitem>
       <para>2007-03-23</para>
       <itemizedlist>
+        <listitem>
+          <para>[dnicholson] - Force <command>ldd</command> to use
+          <command>/bin/bash</command> since it contains Bash-specific
+          syntax.</para>
+        </listitem>
         <listitem>
           <para>[dnicholson] - When readjusting the GCC specs file, ensure
           that GCC will search for the system headers in /usr/include. An

+ 8 - 0
chapter06/glibc.xml

@@ -87,6 +87,14 @@ mv glibc-libidn-&glibc-version; libidn</userinput></screen>
 
 <screen><userinput>patch -Np1 -i ../&glibc-branch_update-patch;</userinput></screen>
 
+    <para>The <command>ldd</command> shell script contains Bash-specific
+    syntax. Change it's default program interpreter to <command>/bin/bash</command>
+    in case another <command>/bin/sh</command> is installed as described in the
+    <ulink url="&blfs-root;view/svn/postlfs/shells.html">Shells</ulink>
+    chapter of the BLFS book:</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>