From 404d6413046353694e39d7935dc0175098b3ea5e Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Fri, 11 May 2012 12:27:48 +0000 Subject: Run fixincludes again, by removing the sed that disabled it. It no longer attempts to fix up host headers. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@9850 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/gcc-pass2.xml | 13 ------------- 1 file changed, 13 deletions(-) (limited to 'chapter05') diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 0fab67c16..6ae16a588 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -58,19 +58,6 @@ cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \ `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include-fixed/limits.h - Under normal circumstances the GCC fixincludes 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 to not require fixing, the - fixincludes script is not required. In fact, running - this script may actually pollute the build environment by - installing fixed headers from the host system into GCC's private include - directory. The running of the fixincludes script can - be suppressed by issuing the following commands: - -cp -v gcc/Makefile.in{,.orig} -sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig > gcc/Makefile.in - For x86 machines, a bootstrap build of GCC uses the compiler flag. Non-bootstrap builds omit this flag by default, and the goal should be to produce a compiler -- cgit v1.2.3-54-g00ecf