Changeset c3dc67c for chapter05/chapter05.xml

Timestamp:

02/14/2004 02:53:12 PM (20 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_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:

21308e2

Parents:

cd1ddd7

Message:

Changing a few SBUs.

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

File:

• chapter05/chapter05.xml (modified) (4 diffs)

chapter05/chapter05.xml

@@ -156 +156 @@
 
 <para>This is important for the reasons mentioned above. It also demonstrates
-that GCC's configure script does not search the $PATH directories to find which
+that GCC's configure script does not search the PATH directories to find which
 tools to use. However, during the actual operation of <command>gcc</command>
 itself, the same search paths are not necessarily used. You can find out which
@@ -170 +170 @@
 building Glibc are the compiler, binary tools and kernel headers. The compiler
 is generally no problem as Glibc will always use the <command>gcc</command>
-found in a $PATH directory. The binary tools and kernel headers can be a little
+found in a PATH directory. The binary tools and kernel headers can be a little
 more troublesome. Therefore we take no risks and use the available configure
 switches to enforce the correct selections. After the run of
@@ -526 +526 @@
 <command>cc</command>. If this works it means the
 <filename class="symlink">/tools/bin/cc</filename> symlink is missing. Revisit
-<xref linkend="ch-tools-gcc-pass1"/> and fix the symlink. Second, ensure your $PATH
+<xref linkend="ch-tools-gcc-pass1"/> and fix the symlink. Second, ensure your PATH
 is correct. You can check this by running <userinput>echo $PATH</userinput> and
 verifying that <filename class="directory">/tools/bin</filename> is at the head
-of the list. If the $PATH is wrong it could mean you're not logged in as user
+of the list. If the PATH is wrong it could mean you're not logged in as user
 <emphasis>lfs</emphasis> or something went wrong back in
 <xref linkend="ch-tools-settingenviron"/>. Third, something may have gone wrong with
@@ -587 +587 @@
 
 <para>Take care <emphasis>not</emphasis> to use
-<emphasis>--strip-unneeded</emphasis> on the libraries -- they would be
-destroyed and you would have to build Glibc all over again.</para>
+<emphasis>--strip-unneeded</emphasis> on the libraries -- the static ones
+would be destroyed and you would have to build the three toolchain packages
+all over again.</para>
 
 <para>To save another couple of megabytes, you can throw away all the