From 72bab458dda2564ba3718a04b5ba6e9784c2da97 Mon Sep 17 00:00:00 2001
From: Gerard Beekmans <gerard@linuxfromscratch.org>
Date: Fri, 3 Jan 2003 02:57:38 +0000
Subject: fix typos - alex' patch

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2274 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter05/gcc-exp.xml | 24 +++++++++++++-----------
 1 file changed, 13 insertions(+), 11 deletions(-)

(limited to 'chapter05')

diff --git a/chapter05/gcc-exp.xml b/chapter05/gcc-exp.xml
index abbf45cae..051d13d14 100644
--- a/chapter05/gcc-exp.xml
+++ b/chapter05/gcc-exp.xml
@@ -18,17 +18,19 @@ This is the equivalent to make LDFLAGS="-static" as we use with other
 packages to compile them statically.</para>
 
 <para><userinput>make install-no-fixedincludes:</userinput>
-This prevents the fixed header files from being installed. This is needed
-because under normal circumstances the GCC installation will run the
-fixincludes scripts which scans your system for header files that need to be
-fixed. Say it finds Glibc header files. It will fix them and will end up in
-$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/ Later on in chapter 6 you
-will install Glibc which will install header files in /usr/include. Next
-you will install other programs which will use Glibc headers. GCC will look
-in /static/lib/gcc-lib before looking in /usr/include, which has the result
-of Glibc header files from your host distribution being found and used which
-are probably incompatible with the Glibc version actually in use on the LFS
-system.</para>
+This prevents the fixincludes script from running. Preventing this is
+necessary because under normal circumstances the GCC installation will run
+the fixincludes script which scans your system for header files that need to
+be fixed. It might find that the Glibc header files of your host system need
+to be fixed. If so, it will fix them and put them in
+<filename>$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2</filename>.
+Later on in chapter 6 you will install Glibc which will put its header
+files in <filename>/usr/include</filename>. Next you will install other
+programs that use the Glibc headers. GCC will look in
+<filename>/static/lib/gcc-lib</filename> before looking in
+<filename>/usr/include</filename>, with the result of finding and using
+the fixed Glibc header files from your host distribution, which are probably
+incompatible with the Glibc version actually used on the LFS system.</para>
 
 <para><userinput>ln -s gcc $LFS/static/bin/cc:</userinput> This
 creates the $LFS/static/bin/gcc symlink, which some packages need.</para>
-- 
cgit v1.2.3-54-g00ecf