Context Navigation

-              r327e4a3
+              r40b88c2
 <itemizedlist>
+<listitem><para>August 29, 2003 [jeremy] - Updated GCC
+to version 3.3.1, including fixes based on Zack's mini-hint
+for GCC 3.3, and patches from his docs.
 <listitem><para>August 28, 2003 [matt] - Updated packages

chapter04/chapter04.xml

-              r327e4a3
+              r40b88c2
 GCC Specs Patch:
+<ulink url="&http;/gcc-3.2.3-specs-4.patch"/>
+GCC MMap Test Patch:
+<ulink url="&http;/gcc-3.2.3-mmap_test.patch"/>
+<ulink url="&http;/gcc-3.3.1-specs.patch"/>
 GCC No Fixincludes Patch:
 <ulink url="&http;/gcc-3.2.3-no_fixincludes.patch"/>
+<ulink url="&http;/gcc-3.3.1-no_fixincludes.patch"/>
 Kbd Patch (&kbd-patch-version;) - &kbd-patch-size;:

-              r327e4a3
+              r40b88c2
 default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
 or modifying them when building GCC.</para>
-<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-mmap_test.patch
-patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch</userinput></screen></para>
 <para>It is recommended by the GCC installation documentation to build

-              r327e4a3
+              r40b88c2
 subdir.</para>
 <para>First correct two problems and make an essential adjustment:</para>
+<para>First correct one problem and make an essential adjustment:</para>
+<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-mmap_test.patch
+patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch
+<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch
 patch -Np1 -i ../gcc-&gcc-specs-version;.patch</userinput></screen></para>

-              r327e4a3
+              r40b88c2
 "/lib/ld-linux.so.2" with "/stage1/lib/ld-linux.so.2".</para>
+<para>Also, because we allowed GCC's "Fixincludes" script to modify our host's
+header files (and this was necessary because of improper use of the __thread
+keyword in some older software), we want to get rid of those modified header
+files, and replace them with pristine ones.</para>
+<para><screen><userinput>GCCDIR=/stage1/lib/gcc-lib/*/*
+rm -rf $GCCDIR/include/*
+cp $GCCDIR/install-tools/include/* $GCCDIR/include
+cp $GCCDIR/install-tools/gsyslimits.h \
+   $GCCDIR/include/syslimits.h
+unset GCCDIR</userinput></screen></para>
 <para>This completes the installation of the self-contained toolchain, which
 can now be used to build the rest of the temporary tools.</para>

-              r327e4a3
+              r40b88c2
 <para>This time we will build both the C and the C++ compiler, so you'll have
 to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
+will unfold into the same directory. The full GCC package contains even more
+will unfold into the same directory. You should likewise extract the
+GCC-testsuite package. The full GCC package contains even more
 compilers. Instructions for building these can be found at
 <ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para>
 <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch
 patch -Np1 -i ../gcc-&gcc-version;-mmap_test.patch</userinput></screen></para>
+</userinput></screen></para>
 <para>GCC's installation documentation recommends to build the package in a

-              r327e4a3
+              r40b88c2
 <!ENTITY aa-gcc-down SYSTEM "../appendixa/gcc-down.xml">
 <!ENTITY gcc-version "3.2.3">
 <!ENTITY gcc-specs-version "3.2.3-specs-4">
+<!ENTITY gcc-version "3.3.1">
+<!ENTITY gcc-specs-version "3.3.1-specs">
 <!ENTITY gcc-depversion "2.95.3">
 <!ENTITY gcc-contversion "3.1">

Note: See TracChangeset for help on using the changeset viewer.