Changeset fa2e693

Timestamp:

09/14/2003 09:16:58 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:

980599d

Parents:

0bf1ea9

Message:

Small grammar adjustments.

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

Location:

chapter05

Files:

• lockingglibc.xml (modified) (1 diff)
• whystatic.xml (modified) (1 diff)

chapter05/lockingglibc.xml

@@ -40 +40 @@
 <para>Lastly, there is a possibility that some include files from the host
 system have found their way into gcc's private include dir. This can happen
-because of GCC's "fixincludes" process which part of the GCC build. We'll
-explain more about this further on in this chapter.  For now, run the
+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>
 

chapter05/whystatic.xml

@@ -44 +44 @@
 <para>But if dynamic linking saves so much space, why then are we linking
 the first two packages in this chapter statically? The reason is to make them
-independent from the libraries on your host system. And the point in that is
-that, if you are pressed for time, you could skip the second passes over GCC
-and Binutils, and just use the static versions to compile the rest of this
-chapter and the first few packages in the next. As in the next chapter we
-will be chrooted to the LFS partition and your host system's Glibc won't be
-available, the programs from GCC and Binutils will need to be self-contained,
-that is statically linked.</para>
+independent from the libraries on your host system. The advantage is that, if
+you are pressed for time, you could skip the second passes over GCC and
+Binutils, and just use the static versions to compile the rest of this chapter
+and the first few packages in the next. In the next chapter we will be
+chrooted to the LFS partition and once inside the chroot environment, the host
+system's Glibc won't be available, thus the programs from GCC and Binutils
+will need to be self-contained, i.e. statically linked. However, we strongly
+advise <emphasis>against</emphasis> skipping the second passes.</para>
 
 </sect1>