Author: matthew
Date: 2005-07-17 07:52:44 -0600 (Sun, 17 Jul 2005)
New Revision: 6545
Modified:
branches/gcc4/BOOK/chapter01/changelog.xml
branches/gcc4/BOOK/chapter05/adjusting.xml
branches/gcc4/BOOK/chapter05/gcc-pass1.xml
branches/gcc4/BOOK/general.ent
Log:
Remove fixinclude sed from gcc pass1, and reintroduce the associated header
removal
Modified: branches/gcc4/BOOK/chapter01/changelog.xml
===================================================================
--- branches/gcc4/BOOK/chapter01/changelog.xml 2005-07-17 04:16:10 UTC (rev
6544)
+++ branches/gcc4/BOOK/chapter01/changelog.xml 2005-07-17 13:52:44 UTC (rev
6545)
@@ -112,6 +112,10 @@
</itemizedlist>
</listitem>
+<listitem><para>July 17th, 2005 [matt]: Removed the fixincludes sed from
+gcc-pass1 as we may need to fix up host's headers. Also reinstate the
+associated removal of pthread.h and sigthread.h.</para></listitem>
+
<listitem><para>July 16th, 2005 [jhuntwork]: Added sed to chapter 5 gcc builds
to force the fixincludes to use the headers in /tools and not the
host.</para></listitem>
Modified: branches/gcc4/BOOK/chapter05/adjusting.xml
===================================================================
--- branches/gcc4/BOOK/chapter05/adjusting.xml 2005-07-17 04:16:10 UTC (rev
6544)
+++ branches/gcc4/BOOK/chapter05/adjusting.xml 2005-07-17 13:52:44 UTC (rev
6545)
@@ -60,6 +60,14 @@
linkend="ch-tools-toolchaintechnotes" role=","/> if
necessary.</para></important>
+<para>There is a possibility that some include files from the host system have
+found their way into GCC's private include dir. This can happen as a result of
+GCC's <quote>fixincludes</quote> process, which runs as part of the GCC build.
+This is explained in more detail later in this chapter. Run the following
+command to eliminate this possibility:</para>
+
+<screen><userinput>rm -f
/tools/lib/gcc/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
+
<caution><para>At this point, it is imperative to stop and ensure that
the basic functions (compiling and linking) of the new toolchain are
working as expected. To perform a sanity check, run the following
Modified: branches/gcc4/BOOK/chapter05/gcc-pass1.xml
===================================================================
--- branches/gcc4/BOOK/chapter05/gcc-pass1.xml 2005-07-17 04:16:10 UTC (rev
6544)
+++ branches/gcc4/BOOK/chapter05/gcc-pass1.xml 2005-07-17 13:52:44 UTC (rev
6545)
@@ -36,12 +36,6 @@
as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
unset them when building GCC.</para>
-<para>The following command adjusts where the gcc fixincludes search for
headers
-so that it fixes only the new headers under /tools, not the ones from your
host system.</para>
-
-<screen><userinput>sed -i '[EMAIL PROTECTED](^NATIVE_SYSTEM_HEADER_DIR
=\)[EMAIL PROTECTED] /tools/[EMAIL PROTECTED]' \
- gcc/Makefile.in</userinput></screen>
-
<para>The GCC documentation recommends building GCC outside of the
source directory in a dedicated build directory:</para>
Modified: branches/gcc4/BOOK/general.ent
===================================================================
--- branches/gcc4/BOOK/general.ent 2005-07-17 04:16:10 UTC (rev 6544)
+++ branches/gcc4/BOOK/general.ent 2005-07-17 13:52:44 UTC (rev 6545)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "GCC4-20050716">
-<!ENTITY releasedate "July 16, 2005">
+<!ENTITY version "GCC4-20050717">
+<!ENTITY releasedate "July 17, 2005">
<!ENTITY milestone "6.2">
<!ENTITY generic-version "gcc4"> <!-- Use "svn", "testing", or "x.y[-pre{x}]"
-->
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
