Changeset 27ced84 for chapter05/gcc-pass2.xml

Timestamp:

10/04/2005 07:56:35 PM (19 years ago)

Author:

Matthew Burgess <matthew@…>

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

795f15c

Parents:

cad7b50

Message:

Prevent GCC's fixincludes from running during chapter 5 pass2 and chapter 6

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

File:

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

chapter05/gcc-pass2.xml

@@ -59 +59 @@
 working.</para>
 
-<para>Under normal circumstances, the GCC <command>fixincludes</command> script
-scans the system for header files that need to be fixed (they may contain syntax
-errors, for example).  The script might find that some Glibc header files on the
-host system need to be fixed, so fixes them and puts them in the GCC private
-include directory. In <xref linkend="chapter-building-system"/>, after the
-newer Glibc has been installed, this private include directory will be searched
-before the system include directory.  This may result in GCC finding the fixed
-headers from the host system, which most likely will not match the Glibc version
-used for the LFS system.</para>
-
-<para>The following command adjusts where the GCC <command>fixincludes</command>
-script searches for headers, so that it fixes only the new headers under
-<filename class="directory">/tools</filename>, not the ones from your host
-system.</para>
+<para>As previously explained in <xref linkend="ch-tools-adjusting"/>,  under
+normal circumstances the GCC <command>fixincludes</command> script is run in
+order to fix potentially broken header files.  As GCC-&gcc-version; and
+Glibc-&glibc-version; have already been installed at this point, and their
+respective header files are known not to require fixing, the
+<command>fixincludes</command> script is not required.  As mentioned previously,
+the script may in fact 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 be suppressed by issuing the following
+commands:</para>
 
 <screen><userinput>cp -v gcc/Makefile.in{,.orig} &amp;&amp;
-sed 's@\(^NATIVE_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g' \
-      gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
+sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
 
 <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>