diff options
| author | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-10-04 19:56:35 +0000 |
|---|---|---|
| committer | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-10-04 19:56:35 +0000 |
| commit | 27ced84613aec2e2718da571c4ce6f5d5aca3966 (patch) | |
| tree | 6521a98173da54f28a1e84669e3b35342b76161a /chapter05/gcc-pass2.xml | |
| parent | cad7b50152d6cb2838d04eee30bf9bc635923873 (diff) | |
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
Diffstat (limited to 'chapter05/gcc-pass2.xml')
| -rw-r--r-- | chapter05/gcc-pass2.xml | 27 |
1 files changed, 11 insertions, 16 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index c52d6b446..904dff8db 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -58,24 +58,19 @@ Binutils until this issue is resolved. Please consult the LFS FAQ at <ulink url="&lfs-root;/lfs/faq.html#no-ptys"/> for more information on how to get PTYs 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} && -sed 's@\(^NATIVE_SYSTEM_HEADER_DIR =\).*@\1 /tools/include@g' \ - gcc/Makefile.in.orig > gcc/Makefile.in</userinput></screen> +sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig > gcc/Makefile.in</userinput></screen> <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/> built GCC with the <option>-fomit-frame-pointer</option> compiler flag. |