Changeset 783c041

Timestamp:

09/17/2003 10:00:04 PM (21 years ago)

Author:

Alex Gronenwoud <alex@…>

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:

2ea93a3

Parents:

552a690

Message:

Minor adjustments to the 'Lock-in' section.

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

File:

• chapter05/lockingglibc.xml (modified) (3 diffs)

chapter05/lockingglibc.xml

@@ -39 +39 @@
 because of GCC's "fixincludes" process which runs as part of the GCC build.
 We'll explain more about this further on in this chapter.  For now, run the
-following commands to eliminate this possibility.</para>
+following commands to eliminate this possibility:</para>
 
 <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>
 
-<caution><para>It is imperative at this point to stop and ensure that the
-basic functionality of the new toolchain is working as expected. We are going
-to perform a simple sanity check:</para>
+<caution><para>It is imperative at this point to stop and ensure that the basic
+functions (compiling and linking) of the new toolchain are working as expected.
+For this we are going to perform a simple sanity check:</para>
 
 <para><screen><userinput>echo 'main(){}' > dummy.c
@@ -51 +51 @@
 readelf -l a.out | grep ': /tools'</userinput></screen></para>
 
-<para>If everything is working correctly, the output of the last command will
-be:</para>
+<para>If everything is working correctly, there should be no errors, and the
+output of the last command will be:</para>
 
 <para><screen>[Requesting program interpreter: /tools/lib/ld-linux.so.2]
 </screen></para>
 
-<para>If you did not receive the output as shown above then something is
+<para>If you did not receive the output as shown above, then something is
 seriously wrong. You will need to investigate and retrace your steps to find
 out where the problem is and correct it. There is no point in continuing
-until this is done. Most likely, something went wrong with the specs file
+until this is done. Most likely something went wrong with the specs file
 amendment above. Note especially that <filename>/tools/lib</filename> appears
 as the prefix of our dynamic linker. Of course, if you are working on a
 platform where the name of the dynamic linker is something other than
-<filename>ld-linux.so.2</filename> then the output will be slightly different.
+<filename>ld-linux.so.2</filename>, then the output will be slightly different.
 </para>
 
@@ -72 +72 @@
 </caution>
 
-<para>This completes the installation of the self-contained toolchain, which
+<para>This completes the installation of the self-contained toolchain, and it
 can now be used to build the rest of the temporary tools.</para>