1 | <sect2><title> </title><para> </para></sect2>
|
---|
2 |
|
---|
3 | <sect2>
|
---|
4 | <title>Re-installation of GCC</title>
|
---|
5 |
|
---|
6 | <para>The tools required to test GCC and Binutils are installed now (Tcl, Expect
|
---|
7 | and DejaGnu). We can continue on rebuilding GCC and Binutils, link them against
|
---|
8 | the new Glibc, and test them properly. One thing to note, however, is that these
|
---|
9 | test suites are highly dependent on properly functioning pseudo terminals (PTYs)
|
---|
10 | which are provided by your host distribution. These days, PTYs are most commonly
|
---|
11 | implemented via the <emphasis>devpts</emphasis> file system. You can quickly
|
---|
12 | check if your host system is set up correctly in this regard by performing a
|
---|
13 | simple test:</para>
|
---|
14 |
|
---|
15 | <para><screen><userinput>expect -c "spawn ls"</userinput></screen></para>
|
---|
16 |
|
---|
17 | <para>If you receive the message:</para>
|
---|
18 |
|
---|
19 | <para><screen>The system has no more ptys. Ask your system administrator to create more.</screen></para>
|
---|
20 |
|
---|
21 | <para>Your host distribution is not set up for proper PTY operation. In this
|
---|
22 | case there is no point in running the test suites for GCC and Binutils until you
|
---|
23 | are able to resolve the issue. You can consult the LFS Wiki at
|
---|
24 | <ulink url="http://wiki.linuxfromscratch.org"/> for more information on how to
|
---|
25 | get PTYs working.</para>
|
---|
26 |
|
---|
27 | <note><para>It's worth pointing out that the GCC test suite we run in this
|
---|
28 | section is considered not as important as the one we run in Chapter 6.</para></note>
|
---|
29 |
|
---|
30 | <para>Unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the same working directory.
|
---|
31 | They will all unfold into a single <filename>gcc-&gcc-version;/</filename>
|
---|
32 | subdir.</para>
|
---|
33 |
|
---|
34 | <para>First correct one problem and make an essential adjustment:</para>
|
---|
35 |
|
---|
36 | <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-2.patch
|
---|
37 | patch -Np1 -i ../gcc-&gcc-specs-version;.patch</userinput></screen></para>
|
---|
38 |
|
---|
39 | <para>The first patch disables the GCC "fixincludes" script. We mentioned this
|
---|
40 | briefly earlier, but a slightly more in-depth explanation of the fixincludes
|
---|
41 | process is warranted here. Under normal circumstances, the GCC fixincludes
|
---|
42 | script scans your system for header files that need to be fixed. It might find
|
---|
43 | that the Glibc header files on your host system need to be fixed, fix them and
|
---|
44 | put them in the GCC private include directory. Then, later on in Chapter 6,
|
---|
45 | after we've installed the newer Glibc, this private include directory would be
|
---|
46 | searched before the system include directory, resulting in GCC finding the
|
---|
47 | fixed headers from the host system, which would most likely not match the Glibc
|
---|
48 | version actually used for the LFS system.</para>
|
---|
49 |
|
---|
50 | <para>The last patch changes GCC's default location of the dynamic linker
|
---|
51 | (typically <filename>ld-linux.so.2</filename>). It also removes
|
---|
52 | <filename class="directory">/usr/include</filename> from GCC's include search
|
---|
53 | path. Patching now rather than adjusting the specs file after installation
|
---|
54 | ensures that our new dynamic linker gets used during the actual build of GCC.
|
---|
55 | That is, all the final (and temporary) binaries created during the build will
|
---|
56 | link against the new Glibc.</para>
|
---|
57 |
|
---|
58 | <important><para>These patches are <emphasis>critical</emphasis> in ensuring a
|
---|
59 | successful overall build. Do not forget to apply them.</para></important>
|
---|
60 |
|
---|
61 | <para>Create a separate build directory again:</para>
|
---|
62 |
|
---|
63 | <para><screen><userinput>mkdir ../gcc-build
|
---|
64 | cd ../gcc-build</userinput></screen></para>
|
---|
65 |
|
---|
66 | <para>Before starting to build GCC, remember to unset any environment
|
---|
67 | variables that override the default optimization flags.</para>
|
---|
68 |
|
---|
69 | <para>Now prepare GCC to be compiled:</para>
|
---|
70 |
|
---|
71 | <para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
72 | --with-local-prefix=/tools \
|
---|
73 | --enable-clocale=gnu --enable-shared \
|
---|
74 | --enable-threads=posix --enable-__cxa_atexit \
|
---|
75 | --enable-languages=c,c++</userinput></screen></para>
|
---|
76 |
|
---|
77 | <para>Compile the package:</para>
|
---|
78 |
|
---|
79 | <para><screen><userinput>make</userinput></screen></para>
|
---|
80 |
|
---|
81 | <para>There is no need to use the <userinput>bootstrap</userinput> target now,
|
---|
82 | as the compiler we're using to compile this GCC was built from the exact same
|
---|
83 | version of the GCC sources we used earlier.</para>
|
---|
84 |
|
---|
85 | <note><para>At this point it is strongly recommended to repeat the sanity check
|
---|
86 | we performed earlier in the chapter. Refer back to the "Locking in" Glibc section
|
---|
87 | and repeat the check. If the results are wrong then most likely, you forgot to
|
---|
88 | apply the abovementioned GCC Specs patch.</para></note>
|
---|
89 |
|
---|
90 | <para>Test the results:</para>
|
---|
91 |
|
---|
92 | <para><screen><userinput>make -k check</userinput></screen></para>
|
---|
93 |
|
---|
94 | <para>The <userinput>-k</userinput> flag is used to make the test suite run
|
---|
95 | through to completion and not stop at the first failure. The GCC test suite is
|
---|
96 | very comprehensive and is almost guaranteed to generate a few failures. To get
|
---|
97 | a summary of the test suite results, run this:</para>
|
---|
98 |
|
---|
99 | <para><screen><userinput>../gcc-&gcc-version;/contrib/test_summary | less</userinput></screen></para>
|
---|
100 |
|
---|
101 | <para>You can compare your results to those posted to the gcc-testresults
|
---|
102 | mailing list for similar configurations to your own. For an example of how
|
---|
103 | current GCC-3.3.1 should look on i686-pc-linux-gnu, see
|
---|
104 | <ulink url="http://gcc.gnu.org/ml/gcc-testresults/2003-08/msg01612.html"/>.</para>
|
---|
105 |
|
---|
106 | <para>Note that the results contain:</para>
|
---|
107 |
|
---|
108 | <screen>* 1 XPASS (unexpected pass) for g++
|
---|
109 | * 1 FAIL for g++
|
---|
110 | * 2 FAIL for gcc
|
---|
111 | * 26 XPASS's for libstdc++</screen>
|
---|
112 |
|
---|
113 | <para>The unexpected pass for g++ is due to the use of
|
---|
114 | <userinput>--enable-__cxa_atexit</userinput>. Apparently not all platforms
|
---|
115 | supported by GCC have support for "__cxa_atexit" in their C libraries, so this
|
---|
116 | test is not always expected to pass.</para>
|
---|
117 |
|
---|
118 | <para>The 26 unexpected passes for libstdc++ are due to the use of
|
---|
119 | <userinput>--enable-clocale=gnu</userinput>, which is the correct choice on
|
---|
120 | Glibc-based systems of versions 2.2.5 and above. The underlying locale support
|
---|
121 | in the GNU C library is superior to that of the otherwise selected "generic"
|
---|
122 | model (which may be applicable if for instance you were using Newlibc, Sun-libc
|
---|
123 | or whatever libc). The libstdc++ test suite is apparently expecting the
|
---|
124 | "generic" model, hence those tests are not always expected to pass.</para>
|
---|
125 |
|
---|
126 | <para>And finally install the package:</para>
|
---|
127 |
|
---|
128 | <para><screen><userinput>make install</userinput></screen></para>
|
---|
129 |
|
---|
130 | </sect2>
|
---|
131 |
|
---|