[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 |
|
---|
[40b88c2] | 12 | <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes.patch
|
---|
[775a268] | 13 | patch -Np1 -i ../gcc-&gcc-specs-version;.patch</userinput></screen></para>
|
---|
| 14 |
|
---|
| 15 | <para>The last patch changes GCC's default location of the dynamic linker,
|
---|
| 16 | a simple substitution of "/lib/ld-linux.so.2" with "/stage1/lib/ld-linux.so.2"
|
---|
| 17 | in <filename>config/i386/linux.h</filename>. Patching now rather than adjusting
|
---|
| 18 | the specs file after installation ensures that our new dynamic linker gets
|
---|
| 19 | used during the actual build of GCC. That is, all the final (and temporary)
|
---|
| 20 | binaries created during the build will link against the new Glibc.</para>
|
---|
| 21 |
|
---|
| 22 | <para>Create a separate build directory again:</para>
|
---|
[bc82645e] | 23 |
|
---|
| 24 | <para><screen><userinput>mkdir ../gcc-build
|
---|
| 25 | cd ../gcc-build</userinput></screen></para>
|
---|
| 26 |
|
---|
[ab6f1859] | 27 | <para>Before starting to build GCC, remember to unset any environment
|
---|
| 28 | variables that override the default optimization flags.</para>
|
---|
| 29 |
|
---|
[775a268] | 30 | <para>Now prepare GCC to be compiled:</para>
|
---|
| 31 |
|
---|
[84a7dc2] | 32 | <para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/stage1 \
|
---|
[bc82645e] | 33 | --with-local-prefix=/stage1 \
|
---|
[6b2f69c] | 34 | --enable-clocale=gnu --enable-shared \
|
---|
[0939e573] | 35 | --enable-threads=posix --enable-__cxa_atexit \
|
---|
[775a268] | 36 | --enable-languages=c,c++</userinput></screen></para>
|
---|
| 37 |
|
---|
| 38 | <para>Compile the package:</para>
|
---|
| 39 |
|
---|
| 40 | <para><screen><userinput>make</userinput></screen></para>
|
---|
| 41 | <para>There is no need to use the <userinput>bootstrap</userinput> target now,
|
---|
| 42 | as the compiler we're using to compile this GCC has been built from the exact
|
---|
| 43 | same sources.</para>
|
---|
| 44 |
|
---|
[ab6f1859] | 45 | <para>Test the results:</para>
|
---|
[775a268] | 46 |
|
---|
| 47 | <para><screen><userinput>make -k check</userinput></screen></para>
|
---|
| 48 |
|
---|
| 49 | <para>The <userinput>-k</userinput> flag is used to make the test suite run
|
---|
| 50 | through to completion and not stop at the first failure. The GCC test suite is
|
---|
| 51 | very comprehensive and is almost guaranteed to generate a few failures. To get
|
---|
| 52 | a summary of the test suite results, run this:</para>
|
---|
| 53 |
|
---|
| 54 | <para><screen><userinput>../gcc-3*/contrib/test_summary | less</userinput></screen></para>
|
---|
| 55 |
|
---|
| 56 | <para>You can compare your results to those posted to the gcc-testresults
|
---|
| 57 | mailing list for similar configurations to your own. For an example of how
|
---|
| 58 | current GCC-3.2.x should look on i686-pc-linux-gnu, see
|
---|
| 59 | <ulink url="http://gcc.gnu.org/ml/gcc-testresults/2003-02/msg00204.html"/>.</para>
|
---|
| 60 |
|
---|
| 61 | <para>Note that the results contain:</para>
|
---|
| 62 |
|
---|
| 63 | <screen>* 1 XPASS (unexpected pass) for g++
|
---|
| 64 | * 26 XPASS's for libstdc++
|
---|
| 65 | * 1 FAIL for libstdc++</screen>
|
---|
| 66 |
|
---|
| 67 | <para>The unexpected pass for g++ is due to the use of
|
---|
| 68 | <userinput>--enable-__cxa_atexit</userinput>. Apparently not all platforms
|
---|
| 69 | supported by GCC have support for "__cxa_atexit" in their C libraries, so this
|
---|
| 70 | test is not always expected to pass.</para>
|
---|
| 71 |
|
---|
| 72 | <para>The 26 unexpected passes for libstdc++ are due to the use of
|
---|
| 73 | <userinput>--enable-clocale=gnu</userinput>, which is the correct choice on
|
---|
| 74 | Glibc-based systems of versions 2.2.5 and above. The underlying locale support
|
---|
| 75 | in the GNU C library is superior to that of the otherwise selected "generic"
|
---|
| 76 | model (which may be applicable if for instance you were using Newlibc, Sun-libc
|
---|
| 77 | or whatever libc). The libstdc++ test suite is apparently expecting the
|
---|
| 78 | "generic" model, hence those tests are not always expected to pass.</para>
|
---|
| 79 |
|
---|
| 80 | <para>The failure for libstdc++ is in
|
---|
| 81 | <filename>26_numerics/c99_classification_macros_c.cc</filename> and is a
|
---|
| 82 | long-standing known failure (since at least January 2002) that the developers
|
---|
| 83 | are apparently unable to easily fix.</para>
|
---|
| 84 |
|
---|
| 85 | <para>And finally install the package:</para>
|
---|
| 86 |
|
---|
| 87 | <para><screen><userinput>make install</userinput></screen></para>
|
---|
[bc82645e] | 88 |
|
---|
| 89 | </sect2>
|
---|
| 90 |
|
---|