[bc82645e] | 1 | <sect2><title> </title><para> </para></sect2>
|
---|
| 2 |
|
---|
| 3 | <sect2>
|
---|
[ab6f1859] | 4 | <title>Re-installation of GCC</title>
|
---|
| 5 |
|
---|
| 6 | <para>Unpack all three GCC tarballs in one and the same working directory.
|
---|
| 7 | They will all unfold into a single <filename>gcc-&gcc-version;/</filename>
|
---|
| 8 | subdir.</para>
|
---|
[bc82645e] | 9 |
|
---|
[40b88c2] | 10 | <para>First correct one problem and make an essential adjustment:</para>
|
---|
[775a268] | 11 |
|
---|
[b19d5f96] | 12 | <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-2.patch
|
---|
[775a268] | 13 | patch -Np1 -i ../gcc-&gcc-specs-version;.patch</userinput></screen></para>
|
---|
| 14 |
|
---|
[be2dd91] | 15 | <para>The first patch disables the GCC "fixincludes" script. We mentioned this
|
---|
| 16 | briefly earlier, but a slightly more in-depth explanation of the fixincludes
|
---|
| 17 | process is warranted here. Under normal circumstances, the GCC fixincludes
|
---|
| 18 | script scans your system for header files that need to be fixed. It might find
|
---|
| 19 | that the Glibc header files on your host system need to be fixed, fix them and
|
---|
| 20 | put them in the GCC private include directory. Then, later on in Chapter 6,
|
---|
| 21 | after we've installed the newer Glibc, this private include directory would be
|
---|
| 22 | searched before the system include directory, resulting in GCC finding the
|
---|
| 23 | fixed headers from the host system, which would most likely not match the Glibc
|
---|
| 24 | version actually used for the LFS system.</para>
|
---|
| 25 |
|
---|
[775a268] | 26 | <para>The last patch changes GCC's default location of the dynamic linker,
|
---|
[148bb04] | 27 | a simple substitution of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2"
|
---|
[775a268] | 28 | in <filename>config/i386/linux.h</filename>. Patching now rather than adjusting
|
---|
| 29 | the specs file after installation ensures that our new dynamic linker gets
|
---|
| 30 | used during the actual build of GCC. That is, all the final (and temporary)
|
---|
| 31 | binaries created during the build will link against the new Glibc.</para>
|
---|
| 32 |
|
---|
| 33 | <para>Create a separate build directory again:</para>
|
---|
[bc82645e] | 34 |
|
---|
| 35 | <para><screen><userinput>mkdir ../gcc-build
|
---|
| 36 | cd ../gcc-build</userinput></screen></para>
|
---|
| 37 |
|
---|
[ab6f1859] | 38 | <para>Before starting to build GCC, remember to unset any environment
|
---|
| 39 | variables that override the default optimization flags.</para>
|
---|
| 40 |
|
---|
[775a268] | 41 | <para>Now prepare GCC to be compiled:</para>
|
---|
| 42 |
|
---|
[148bb04] | 43 | <para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
| 44 | --with-local-prefix=/tools \
|
---|
[6b2f69c] | 45 | --enable-clocale=gnu --enable-shared \
|
---|
[0939e573] | 46 | --enable-threads=posix --enable-__cxa_atexit \
|
---|
[775a268] | 47 | --enable-languages=c,c++</userinput></screen></para>
|
---|
| 48 |
|
---|
| 49 | <para>Compile the package:</para>
|
---|
| 50 |
|
---|
| 51 | <para><screen><userinput>make</userinput></screen></para>
|
---|
| 52 | <para>There is no need to use the <userinput>bootstrap</userinput> target now,
|
---|
| 53 | as the compiler we're using to compile this GCC has been built from the exact
|
---|
| 54 | same sources.</para>
|
---|
| 55 |
|
---|
[ab6f1859] | 56 | <para>Test the results:</para>
|
---|
[775a268] | 57 |
|
---|
| 58 | <para><screen><userinput>make -k check</userinput></screen></para>
|
---|
| 59 |
|
---|
| 60 | <para>The <userinput>-k</userinput> flag is used to make the test suite run
|
---|
| 61 | through to completion and not stop at the first failure. The GCC test suite is
|
---|
| 62 | very comprehensive and is almost guaranteed to generate a few failures. To get
|
---|
| 63 | a summary of the test suite results, run this:</para>
|
---|
| 64 |
|
---|
| 65 | <para><screen><userinput>../gcc-3*/contrib/test_summary | less</userinput></screen></para>
|
---|
| 66 |
|
---|
| 67 | <para>You can compare your results to those posted to the gcc-testresults
|
---|
| 68 | mailing list for similar configurations to your own. For an example of how
|
---|
[bef49bf] | 69 | current GCC-3.3.1 should look on i686-pc-linux-gnu, see
|
---|
| 70 | <ulink url="http://gcc.gnu.org/ml/gcc-testresults/2003-08/msg01612.html"/>.</para>
|
---|
[775a268] | 71 |
|
---|
| 72 | <para>Note that the results contain:</para>
|
---|
| 73 |
|
---|
| 74 | <screen>* 1 XPASS (unexpected pass) for g++
|
---|
[9e24a7d] | 75 | * 1 FAIL for g++
|
---|
| 76 | * 2 FAIL for gcc
|
---|
| 77 | * 26 XPASS's for libstdc++</screen>
|
---|
[775a268] | 78 |
|
---|
| 79 | <para>The unexpected pass for g++ is due to the use of
|
---|
| 80 | <userinput>--enable-__cxa_atexit</userinput>. Apparently not all platforms
|
---|
| 81 | supported by GCC have support for "__cxa_atexit" in their C libraries, so this
|
---|
| 82 | test is not always expected to pass.</para>
|
---|
| 83 |
|
---|
| 84 | <para>The 26 unexpected passes for libstdc++ are due to the use of
|
---|
| 85 | <userinput>--enable-clocale=gnu</userinput>, which is the correct choice on
|
---|
| 86 | Glibc-based systems of versions 2.2.5 and above. The underlying locale support
|
---|
| 87 | in the GNU C library is superior to that of the otherwise selected "generic"
|
---|
| 88 | model (which may be applicable if for instance you were using Newlibc, Sun-libc
|
---|
| 89 | or whatever libc). The libstdc++ test suite is apparently expecting the
|
---|
| 90 | "generic" model, hence those tests are not always expected to pass.</para>
|
---|
| 91 |
|
---|
| 92 | <para>And finally install the package:</para>
|
---|
| 93 |
|
---|
| 94 | <para><screen><userinput>make install</userinput></screen></para>
|
---|
[bc82645e] | 95 |
|
---|
| 96 | </sect2>
|
---|
| 97 |
|
---|