source: chapter05/gcc-pass2-inst.xml@ 1f30432

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 1f30432 was ab6f1859, checked in by Alex Gronenwoud <alex@…>, 21 years ago

small things around coreutils and bugs #518 and #520

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2668 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

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