Changeset f57e3d1 for chapter05

Timestamp:

10/07/2003 12:41:12 AM (21 years ago)

Author:

Greg Schafer <greg@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

f861982

Parents:

04a3351

Message:

Rearrange "How things are going to be done" section. Simplify seds in "Locking in Glibc" and "Re-adjusting the toolchain" sections. Miscellaneous other fixes.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2931 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:

chapter05

Files:

• gcc-pass2-inst.xml (modified) (1 diff)
• lockingglibc.xml (modified) (1 diff)
• toolchaintechnotes.xml (modified) (1 diff)

chapter05/gcc-pass2-inst.xml

@@ -156 +156 @@
 we performed earlier in the chapter. Refer back to the "Locking in" Glibc section
 and repeat the check. If the results are wrong then most likely, you forgot to
-apply the abovementioned GCC Specs patch.</para></note>
+apply the above mentioned GCC Specs patch.</para></note>
 
 </sect2>

chapter05/lockingglibc.xml

@@ -24 +24 @@
    
 <para><screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs
-sed -e 's@/lib/ld.so.1@/tools/lib/ld.so.1@g' \
-&nbsp;&nbsp;&nbsp;&nbsp;-e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \
+sed -e 's@/lib/ld-linux.so.2@/tools/lib/ld-linux.so.2@g' \
 &nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE > tempspecfile
 mv tempspecfile $SPECFILE
 unset SPECFILE</userinput></screen></para>
 
-<para>We recommend that you cut-and-paste the above rather than try and type it 
-all in. Or you can edit the specs file by hand if you want to: just replace 
-"/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2" and "/lib/ld.so.1" with 
-"/tools/lib/ld.so.1".</para>
+<para>We recommend that you cut-and-paste the above rather than try and type it
+all in. Or you can edit the specs file by hand if you want to: just replace any
+occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2".</para>
+
+<important><para>If you are working on a platform where the name of the dynamic
+linker is something other than <filename>ld-linux.so.2</filename>, you
+<emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
+name of your platform's dynamic linker in the above commands. Refer back to the
+"Toolchain technical notes" section if necessary.</para></important>
 
 <para>Lastly, there is a possibility that some include files from the host

chapter05/toolchaintechnotes.xml

@@ -123 +123 @@
 <filename class="directory">/tools/lib</filename>. This last step is
 <emphasis>vital</emphasis> to the whole process. As mentioned above, a
-hard-wired path to a dynamic linker is embedded into every executable binary.
-You can inspect this by running:
+hard-wired path to a dynamic linker is embedded into every ELF shared
+executable. You can inspect this by running:
 <userinput>`readelf -l &lt;name of binary&gt; | grep interpreter`</userinput>.
 By amending the GCC specs file, we are ensuring that every program compiled from