[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
[9652249] | 6 | <sect1 id="ch-tools-gcc-pass2" role="wrap">
|
---|
[673b0d8] | 7 | <title>GCC-&gcc-version; - Pass 2</title>
|
---|
| 8 | <?dbhtml filename="gcc-pass2.html"?>
|
---|
[bc82645e] | 9 |
|
---|
[673b0d8] | 10 | <indexterm zone="ch-tools-gcc-pass2">
|
---|
| 11 | <primary sortas="a-GCC">GCC</primary>
|
---|
| 12 | <secondary>tools, pass 2</secondary></indexterm>
|
---|
[bc82645e] | 13 |
|
---|
[9652249] | 14 | <sect2 role="package"><title/>
|
---|
[73aedd1d] | 15 |
|
---|
[9652249] | 16 | <segmentedlist>
|
---|
| 17 | <segtitle>&buildtime;</segtitle>
|
---|
| 18 | <segtitle>&diskspace;</segtitle>
|
---|
| 19 | <seglistitem><seg>11.0 SBU</seg><seg>274 MB</seg></seglistitem>
|
---|
| 20 | </segmentedlist>
|
---|
[73aedd1d] | 21 |
|
---|
[6e41459] | 22 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
|
---|
| 23 |
|
---|
[9652249] | 24 | </sect2>
|
---|
| 25 |
|
---|
| 26 | <sect2 role="installation">
|
---|
[73aedd1d] | 27 | <title>Re-installation of GCC</title>
|
---|
| 28 |
|
---|
[24a08b9] | 29 | <para>This package is known to have issues when its default
|
---|
| 30 | optimization flags (including the <parameter>-march</parameter> and
|
---|
| 31 | <parameter>-mcpu</parameter> options) are changed. If any environment
|
---|
| 32 | variables that override default optimizations have been defined, such
|
---|
| 33 | as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
|
---|
| 34 | unset them when building GCC.</para>
|
---|
| 35 |
|
---|
[69993f4] | 36 | <para>The tools required to test GCC and Binutils—Tcl, Expect
|
---|
| 37 | and DejaGNU—are installed now. GCC and Binutils can now be
|
---|
| 38 | rebuilt, linking them against the new Glibc and testing them properly
|
---|
| 39 | (if running the test suites in this chapter). Please note that these
|
---|
| 40 | test suites are highly dependent on properly functioning PTYs which
|
---|
| 41 | are provided by the host. PTYs are most commonly implemented via the
|
---|
| 42 | <systemitem class="filesystem">devpts</systemitem> file system. Check
|
---|
| 43 | to see if the host system is set up correctly in this regard by
|
---|
| 44 | performing a quick test:</para>
|
---|
[73aedd1d] | 45 |
|
---|
| 46 | <screen><userinput>expect -c "spawn ls"</userinput></screen>
|
---|
| 47 |
|
---|
[ede9b9b] | 48 | <para>The response might be:</para>
|
---|
[73aedd1d] | 49 |
|
---|
[c863747] | 50 | <screen><computeroutput>The system has no more ptys.
|
---|
| 51 | Ask your system administrator to create more.</computeroutput></screen>
|
---|
[73aedd1d] | 52 |
|
---|
[6e41459] | 53 | <para>If the above message is received, the host does not have its
|
---|
| 54 | PTYs set up properly. In this case, there is no point in running the
|
---|
| 55 | test suites for GCC and Binutils until this issue is resolved. Please
|
---|
| 56 | consult the LFS Wiki at <ulink url="&wiki-root;"/> for more
|
---|
| 57 | information on how to get PTYs working.</para>
|
---|
[73aedd1d] | 58 |
|
---|
[6e41459] | 59 | <para>Because the C and the C++ compilers will be built, unpack both
|
---|
[69993f4] | 60 | the core and the g++ tarballs (as well as test suite, if you want to
|
---|
[6e41459] | 61 | run the tests). By unpacking them in the working directory, they will
|
---|
| 62 | all unfold into a single <filename
|
---|
| 63 | class="directory">gcc-&gcc-version;/</filename> subdirectory.</para>
|
---|
[73aedd1d] | 64 |
|
---|
[6e41459] | 65 | <para>First correct a known problem and make an essential adjustment:</para>
|
---|
[73aedd1d] | 66 |
|
---|
[e075967] | 67 | <screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-1.patch
|
---|
| 68 | patch -Np1 -i ../gcc-&gcc-version;-specs-1.patch</userinput></screen>
|
---|
[673b0d8] | 69 |
|
---|
[6e41459] | 70 | <para>The first patch disables the GCC <command>fixincludes</command>
|
---|
| 71 | script. This was briefly mentioned earlier, but a more in-depth
|
---|
| 72 | explanation of the fixincludes process is warranted here. Under normal
|
---|
| 73 | circumstances, the GCC <command>fixincludes</command> script scans the
|
---|
| 74 | system for header files that need to be fixed. It might find that some
|
---|
| 75 | Glibc header files on the host system need to be fixed, and will fix
|
---|
| 76 | them and put them in the GCC private include directory. In <xref
|
---|
[69993f4] | 77 | linkend="chapter-building-system"/>, after the newer Glibc has been
|
---|
[6e41459] | 78 | installed, this private include directory will be searched before the
|
---|
| 79 | system include directory. This may result in GCC finding the fixed
|
---|
| 80 | headers from the host system, which most likely will not match the
|
---|
| 81 | Glibc version used for the LFS system.</para>
|
---|
| 82 |
|
---|
| 83 | <para>The second patch changes GCC's default location of the dynamic
|
---|
| 84 | linker (typically <filename>ld-linux.so.2</filename>). It also removes
|
---|
| 85 | <filename class="directory">/usr/include</filename> from GCC's include
|
---|
| 86 | search path. Patching now rather than adjusting the specs file after
|
---|
| 87 | installation ensures that the new dynamic linker is used during the
|
---|
| 88 | actual build of GCC. That is, all of the final (and temporary)
|
---|
| 89 | binaries created during the build will link against the new
|
---|
| 90 | Glibc.</para>
|
---|
| 91 |
|
---|
| 92 | <important><para>The above patches are critical in ensuring a
|
---|
| 93 | successful overall build. Do not forget to apply
|
---|
| 94 | them.</para></important>
|
---|
[73aedd1d] | 95 |
|
---|
| 96 | <para>Create a separate build directory again:</para>
|
---|
| 97 |
|
---|
| 98 | <screen><userinput>mkdir ../gcc-build
|
---|
| 99 | cd ../gcc-build</userinput></screen>
|
---|
| 100 |
|
---|
| 101 | <para>Before starting to build GCC, remember to unset any environment
|
---|
| 102 | variables that override the default optimization flags.</para>
|
---|
| 103 |
|
---|
[d27a27b] | 104 | <para>Now prepare GCC for compilation:</para>
|
---|
[73aedd1d] | 105 |
|
---|
[673b0d8] | 106 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
[9dfc02f] | 107 | --libexecdir=/tools/lib --with-local-prefix=/tools \
|
---|
[c863747] | 108 | --enable-clocale=gnu --enable-shared \
|
---|
| 109 | --enable-threads=posix --enable-__cxa_atexit \
|
---|
| 110 | --enable-languages=c,c++ --disable-libstdcxx-pch</userinput></screen>
|
---|
[73aedd1d] | 111 |
|
---|
| 112 | <para>The meaning of the new configure options:</para>
|
---|
| 113 |
|
---|
[9652249] | 114 | <variablelist>
|
---|
| 115 | <varlistentry>
|
---|
[574b0ea] | 116 | <term><parameter>--enable-clocale=gnu</parameter></term>
|
---|
[6e41459] | 117 | <listitem><para>This option ensures the correct locale model is
|
---|
| 118 | selected for the C++ libraries under all circumstances. If the
|
---|
| 119 | configure script finds the <emphasis>de_DE</emphasis> locale installed, it will select the
|
---|
| 120 | correct gnu locale model. However, if the <emphasis>de_DE</emphasis> locale is not
|
---|
| 121 | installed, there is the risk of building Application Binary Interface
|
---|
| 122 | (ABI)-incompatible C++ libraries because the incorrect generic locale
|
---|
| 123 | model may be selected.</para></listitem>
|
---|
[9652249] | 124 | </varlistentry>
|
---|
[ede9b9b] | 125 |
|
---|
[9652249] | 126 | <varlistentry>
|
---|
[574b0ea] | 127 | <term><parameter>--enable-threads=posix</parameter></term>
|
---|
[6e41459] | 128 | <listitem><para>This enables C++ exception handling for multi-threaded
|
---|
| 129 | code.</para></listitem>
|
---|
[9652249] | 130 | </varlistentry>
|
---|
[73aedd1d] | 131 |
|
---|
[9652249] | 132 | <varlistentry>
|
---|
[574b0ea] | 133 | <term><parameter>--enable-__cxa_atexit</parameter></term>
|
---|
[6e41459] | 134 | <listitem><para>This option allows use of
|
---|
| 135 | <emphasis>__cxa_atexit</emphasis>, rather than
|
---|
| 136 | <emphasis>atexit</emphasis>, to register C++ destructors for local
|
---|
| 137 | statics and global objects. This option is essential for fully
|
---|
| 138 | standards-compliant handling of destructors. It also affects the C++
|
---|
[69993f4] | 139 | ABI, and therefore results in C++ shared libraries and C++ programs
|
---|
[6e41459] | 140 | that are interoperable with other Linux
|
---|
[73aedd1d] | 141 | distributions.</para></listitem>
|
---|
[9652249] | 142 | </varlistentry>
|
---|
[73aedd1d] | 143 |
|
---|
[9652249] | 144 | <varlistentry>
|
---|
[574b0ea] | 145 | <term><parameter>--enable-languages=c,c++</parameter></term>
|
---|
[9652249] | 146 | <listitem><para>This option
|
---|
[ede9b9b] | 147 | ensures that both the C and C++ compilers are built.</para></listitem>
|
---|
[9652249] | 148 | </varlistentry>
|
---|
[32a531e] | 149 |
|
---|
[9652249] | 150 | <varlistentry>
|
---|
[574b0ea] | 151 | <term><parameter>--disable-libstdcxx-pch</parameter></term>
|
---|
[6e41459] | 152 | <listitem><para>Do not build the pre-compiled header (PCH) for
|
---|
| 153 | libstdc++. It takes up a lot of space, and we have no use for
|
---|
| 154 | it.</para></listitem>
|
---|
[9652249] | 155 | </varlistentry>
|
---|
| 156 | </variablelist>
|
---|
[73aedd1d] | 157 |
|
---|
| 158 | <para>Compile the package:</para>
|
---|
| 159 |
|
---|
| 160 | <screen><userinput>make</userinput></screen>
|
---|
| 161 |
|
---|
[6e41459] | 162 | <para>There is no need to use the <parameter>bootstrap</parameter>
|
---|
| 163 | target now because the compiler being used to compile this GCC was
|
---|
| 164 | built from the exact same version of the GCC sources used
|
---|
| 165 | earlier.</para>
|
---|
[73aedd1d] | 166 |
|
---|
[6e41459] | 167 | <para>Compilation is now complete. As previously mentioned, running
|
---|
| 168 | the test suites for the temporary tools compiled in this chapter is
|
---|
| 169 | not mandatory. To run the GCC test suite anyway, use the following
|
---|
| 170 | command:</para>
|
---|
[73aedd1d] | 171 |
|
---|
| 172 | <screen><userinput>make -k check</userinput></screen>
|
---|
| 173 |
|
---|
[574b0ea] | 174 | <para>The <parameter>-k</parameter> flag is used to make the test suite run
|
---|
[6e41459] | 175 | through to completion and not stop at the first failure. The GCC test
|
---|
| 176 | suite is very comprehensive and is almost guaranteed to generate a few
|
---|
| 177 | failures. To receive a summary of the test suite results, run:</para>
|
---|
[73aedd1d] | 178 |
|
---|
[673b0d8] | 179 | <screen><userinput>../gcc-&gcc-version;/contrib/test_summary</userinput></screen>
|
---|
[e8692c5e] | 180 |
|
---|
[6e41459] | 181 | <para>For only the summaries, pipe the output through
|
---|
| 182 | <userinput>grep -A7 Summ</userinput>.</para>
|
---|
[73aedd1d] | 183 |
|
---|
[6e41459] | 184 | <para>Results can be compared to those posted to the gcc-testresults
|
---|
| 185 | mailing list to see similar configurations to the one being built. For
|
---|
| 186 | an example of how current GCC-&gcc-version; should look on
|
---|
| 187 | i686-pc-linux-gnu, see <ulink
|
---|
| 188 | url="http://gcc.gnu.org/ml/gcc-testresults/2004-07/msg00179.html"/>.</para>
|
---|
[ede9b9b] | 189 |
|
---|
[69993f4] | 190 | <para>A few unexpected failures cannot always be avoided. The
|
---|
[6e41459] | 191 | GCC developers are usually aware of these issues, but have not
|
---|
| 192 | resolved them yet. Unless the test results are vastly different from
|
---|
| 193 | those at the above URL, it is safe to continue.</para>
|
---|
[73aedd1d] | 194 |
|
---|
[6e41459] | 195 | <para>Install the package:</para>
|
---|
[73aedd1d] | 196 |
|
---|
| 197 | <screen><userinput>make install</userinput></screen>
|
---|
| 198 |
|
---|
[6e41459] | 199 | <note><para>At this point it is strongly recommended to repeat the
|
---|
| 200 | sanity check we performed earlier in this chapter. Refer back to <xref
|
---|
| 201 | linkend="ch-tools-adjusting"/> and repeat the test compilation. If
|
---|
| 202 | the result is wrong, the most likely reason is that the GCC Specs
|
---|
| 203 | patch was not properly applied.</para></note>
|
---|
[73aedd1d] | 204 |
|
---|
| 205 | </sect2>
|
---|
[bc82645e] | 206 |
|
---|
[9652249] | 207 | <sect2 role="content"><title/>
|
---|
[69993f4] | 208 | <para>Details on this package are located in <xref linkend="contents-gcc"/>.</para>
|
---|
[0868461] | 209 | </sect2>
|
---|
[5888299] | 210 |
|
---|
[bc82645e] | 211 | </sect1>
|
---|
[6e41459] | 212 |
|
---|