Browse Source

added fixincludes explanation

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2180 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Gerard Beekmans 23 years ago
parent
commit
ac68bd3dd2
1 changed files with 11 additions and 1 deletions
  1. 11 1
      chapter05/gcc-exp.xml

+ 11 - 1
chapter05/gcc-exp.xml

@@ -7,7 +7,17 @@ This patch fixes a few bugs. In particular it contains the "copy fix" and
 <ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para>
 
 <para><userinput>patch -Np1 -i ../gcc-3.2-nofixincludes-2.patch:</userinput>
-This prevents the fixincludes script from running.</para>
+This prevents the fixincludes script from running. 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/3.2. 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, whichhas 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>
 
 <para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard
 codes some paths while compiling and so we need to pass /static as the