aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/gcc-pass2-inst.xml
diff options
context:
space:
mode:
authorGreg Schafer <greg@linuxfromscratch.org>2003-09-26 04:11:08 +0000
committerGreg Schafer <greg@linuxfromscratch.org>2003-09-26 04:11:08 +0000
commit1cb7ced1c435847432511e06989b1d650912d921 (patch)
tree09e8eafec67f9871dc0456709f8955f07bfdd496 /chapter05/gcc-pass2-inst.xml
parent6952b96fa29f30559ef1ac6d17f630ea2efc007a (diff)
Small fixups across the board.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2883 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass2-inst.xml')
-rw-r--r--chapter05/gcc-pass2-inst.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml
index bd2ba4428..a22419cb0 100644
--- a/chapter05/gcc-pass2-inst.xml
+++ b/chapter05/gcc-pass2-inst.xml
@@ -40,7 +40,7 @@ patch -Np1 -i ../gcc-&gcc-specs-version;.patch</userinput></screen></para>
briefly earlier, but a slightly more in-depth explanation of the fixincludes
process is warranted here. Under normal circumstances, the GCC fixincludes
script scans your system for header files that need to be fixed. It might find
-that the Glibc header files on your host system need to be fixed, fix them and
+that some Glibc header files on your host system need to be fixed, fix them and
put them in the GCC private include directory. Then, later on in Chapter 6,
after we've installed the newer Glibc, this private include directory would be
searched before the system include directory, resulting in GCC finding the