Changeset 550f9f4

Timestamp:

05/24/2009 06:09:10 PM (15 years ago)

Author:

Gerard Beekmans <gerard@…>

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.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, 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:

4396ba2

Parents:

a094de3

Message:

Minor edit.

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

File:

• chapter05/gcc-pass2.xml (modified) (1 diff)

chapter05/gcc-pass2.xml

@@ -58 +58 @@
     and Glibc-&glibc-version; have already been installed at this point, and
     their respective header files are known to not require fixing, the
-    <command>fixincludes</command> script is not required. As mentioned
-    previously, the script may in fact pollute the build environment by
+    <command>fixincludes</command> script is not required. In fact, running
+    this script may actually pollute the build environment by
     installing fixed headers from the host system into GCC's private include
     directory. The running of the <command>fixincludes</command> script can