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