[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[d096eb1] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[d096eb1] | 7 |
|
---|
[9652249] | 8 | <sect1 id="ch-tools-gcc-pass2" role="wrap">
|
---|
[d096eb1] | 9 | <?dbhtml filename="gcc-pass2.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>GCC-&gcc-version; - Pass 2</title>
|
---|
| 12 |
|
---|
| 13 | <indexterm zone="ch-tools-gcc-pass2">
|
---|
| 14 | <primary sortas="a-GCC">GCC</primary>
|
---|
| 15 | <secondary>tools, pass 2</secondary>
|
---|
| 16 | </indexterm>
|
---|
| 17 |
|
---|
| 18 | <sect2 role="package">
|
---|
| 19 | <title/>
|
---|
[bc82645e] | 20 |
|
---|
[d096eb1] | 21 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
|
---|
| 22 | href="../chapter06/gcc.xml"
|
---|
| 23 | xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
|
---|
[81fd230] | 24 |
|
---|
[d096eb1] | 25 | <segmentedlist>
|
---|
| 26 | <segtitle>&buildtime;</segtitle>
|
---|
| 27 | <segtitle>&diskspace;</segtitle>
|
---|
[73aedd1d] | 28 |
|
---|
[d096eb1] | 29 | <seglistitem>
|
---|
| 30 | <seg>11.0 SBU</seg>
|
---|
| 31 | <seg>292 MB</seg>
|
---|
| 32 | </seglistitem>
|
---|
| 33 | </segmentedlist>
|
---|
[73aedd1d] | 34 |
|
---|
[d096eb1] | 35 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
|
---|
| 36 | href="../chapter06/gcc.xml"
|
---|
| 37 | xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
|
---|
[81fd230] | 38 |
|
---|
[d096eb1] | 39 | </sect2>
|
---|
[9652249] | 40 |
|
---|
[d096eb1] | 41 | <sect2 role="installation">
|
---|
| 42 | <title>Re-installation of GCC</title>
|
---|
[73aedd1d] | 43 |
|
---|
[d096eb1] | 44 | <para>The tools required to test GCC and Binutils—Tcl, Expect
|
---|
| 45 | and DejaGNU—are installed now. GCC and Binutils can now be
|
---|
| 46 | rebuilt, linking them against the new Glibc and testing them properly
|
---|
| 47 | (if running the test suites in this chapter). Please note that these
|
---|
| 48 | test suites are highly dependent on properly functioning PTYs which
|
---|
| 49 | are provided by the host. PTYs are most commonly implemented via the
|
---|
| 50 | <systemitem class="filesystem">devpts</systemitem> file system. Check
|
---|
| 51 | to see if the host system is set up correctly in this regard by
|
---|
| 52 | performing a quick test:</para>
|
---|
[73aedd1d] | 53 |
|
---|
| 54 | <screen><userinput>expect -c "spawn ls"</userinput></screen>
|
---|
| 55 |
|
---|
[d096eb1] | 56 | <para>The response might be:</para>
|
---|
[81fd230] | 57 |
|
---|
[d096eb1] | 58 | <screen><computeroutput>The system has no more ptys.
|
---|
[81fd230] | 59 | Ask your system administrator to create more.</computeroutput></screen>
|
---|
| 60 |
|
---|
[d096eb1] | 61 | <para>If the above message is received, the host does not have its PTYs
|
---|
| 62 | set up properly. In this case, there is no point in running the test
|
---|
| 63 | suites for GCC and Binutils until this issue is resolved. Please consult
|
---|
| 64 | the LFS FAQ at <ulink url="&lfs-root;/lfs/faq.html#no-ptys"/> for more
|
---|
| 65 | information on how to get PTYs working.</para>
|
---|
| 66 |
|
---|
| 67 | <para>As previously explained in <xref linkend="ch-tools-adjusting"/>,
|
---|
| 68 | under normal circumstances the GCC <command>fixincludes</command> script
|
---|
| 69 | is run in order to fix potentially broken header files. As GCC-&gcc-version;
|
---|
| 70 | and Glibc-&glibc-version; have already been installed at this point, and
|
---|
| 71 | their respective header files are known to not require fixing, the
|
---|
| 72 | <command>fixincludes</command> script is not required. As mentioned
|
---|
| 73 | previously, the script may in fact pollute the build environment by
|
---|
| 74 | installing fixed headers from the host system into GCC's private include
|
---|
| 75 | directory. The running of the <command>fixincludes</command> script can
|
---|
| 76 | be suppressed by issuing the following commands:</para>
|
---|
[2e02c35] | 77 |
|
---|
[5998892] | 78 | <screen><userinput>cp -v gcc/Makefile.in{,.orig} &&
|
---|
[27ced84] | 79 | sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig > gcc/Makefile.in</userinput></screen>
|
---|
[2e02c35] | 80 |
|
---|
[d096eb1] | 81 | <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>
|
---|
| 82 | built GCC with the <option>-fomit-frame-pointer</option> compiler flag.
|
---|
| 83 | Non-bootstrap builds omit this flag by default, so apply the following
|
---|
| 84 | <command>sed</command> to use it in order to ensure consistent compiler
|
---|
| 85 | builds.</para>
|
---|
[2e02c35] | 86 |
|
---|
[5998892] | 87 | <screen><userinput>cp -v gcc/Makefile.in{,.tmp} &&
|
---|
[2e02c35] | 88 | sed 's/^XCFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in.tmp \
|
---|
[d096eb1] | 89 | > gcc/Makefile.in</userinput></screen>
|
---|
[2e02c35] | 90 |
|
---|
[d096eb1] | 91 | <para>Apply the following patch to change the location of GCC's default
|
---|
| 92 | dynamiclinker (typically <filename
|
---|
| 93 | class="libraryfile">ld-linux.so.2</filename>):</para>
|
---|
[2e02c35] | 94 |
|
---|
| 95 | <screen><userinput>patch -Np1 -i ../&gcc-specs-patch;</userinput></screen>
|
---|
| 96 |
|
---|
[d096eb1] | 97 | <para>The above patch also removes <filename
|
---|
| 98 | class="directory">/usr/include</filename> from GCC's include search path.
|
---|
| 99 | Patching now rather than adjusting the specs file after installation
|
---|
| 100 | ensures that the new dynamic linker is used during the actual build of
|
---|
| 101 | GCC. That is, all of the binaries created during the build will link
|
---|
| 102 | against the new Glibc.</para>
|
---|
[81fd230] | 103 |
|
---|
[d096eb1] | 104 | <important>
|
---|
| 105 | <para>The above patch is critical in ensuring a successful overall
|
---|
| 106 | build. Do not forget to apply it.</para>
|
---|
| 107 | </important>
|
---|
[81fd230] | 108 |
|
---|
[d096eb1] | 109 | <para>Create a separate build directory again:</para>
|
---|
[73aedd1d] | 110 |
|
---|
[5998892] | 111 | <screen><userinput>mkdir -v ../gcc-build
|
---|
[73aedd1d] | 112 | cd ../gcc-build</userinput></screen>
|
---|
| 113 |
|
---|
[d096eb1] | 114 | <para>Before starting to build GCC, remember to unset any environment
|
---|
| 115 | variables that override the default optimization flags.</para>
|
---|
[81fd230] | 116 |
|
---|
[d096eb1] | 117 | <para>Now prepare GCC for compilation:</para>
|
---|
[73aedd1d] | 118 |
|
---|
[673b0d8] | 119 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
|
---|
[f684ec6c] | 120 | --with-local-prefix=/tools --enable-clocale=gnu \
|
---|
| 121 | --enable-shared --enable-threads=posix \
|
---|
| 122 | --enable-__cxa_atexit --enable-languages=c,c++ \
|
---|
| 123 | --disable-libstdcxx-pch</userinput></screen>
|
---|
[73aedd1d] | 124 |
|
---|
[d096eb1] | 125 | <variablelist>
|
---|
| 126 | <title>The meaning of the new configure options:</title>
|
---|
| 127 |
|
---|
| 128 | <varlistentry>
|
---|
| 129 | <term><parameter>--enable-clocale=gnu</parameter></term>
|
---|
| 130 | <listitem>
|
---|
| 131 | <para>This option ensures the correct locale model is selected
|
---|
| 132 | for the C++ libraries under all circumstances. If the configure
|
---|
| 133 | script finds the <emphasis>de_DE</emphasis> locale installed,
|
---|
| 134 | it will select the correct gnu locale model. However, if the
|
---|
| 135 | <emphasis>de_DE</emphasis> locale is not installed, there is the
|
---|
| 136 | risk of building Application Binary Interface (ABI)-incompatible
|
---|
| 137 | C++ libraries because the incorrect generic locale model may be
|
---|
| 138 | selected.</para>
|
---|
| 139 | </listitem>
|
---|
| 140 | </varlistentry>
|
---|
| 141 |
|
---|
| 142 | <varlistentry>
|
---|
| 143 | <term><parameter>--enable-threads=posix</parameter></term>
|
---|
| 144 | <listitem>
|
---|
| 145 | <para>This enables C++ exception handling for multi-threaded code.</para>
|
---|
| 146 | </listitem>
|
---|
| 147 | </varlistentry>
|
---|
| 148 |
|
---|
| 149 | <varlistentry>
|
---|
| 150 | <term><parameter>--enable-__cxa_atexit</parameter></term>
|
---|
| 151 | <listitem>
|
---|
| 152 | <para>This option allows use of <function>__cxa_atexit</function>,
|
---|
| 153 | rather than <function>atexit</function>, to register C++ destructors
|
---|
| 154 | for local statics and global objects. This option is essential for
|
---|
| 155 | fully standards-compliant handling of destructors. It also affects
|
---|
| 156 | the C++ ABI, and therefore results in C++ shared libraries and C++
|
---|
| 157 | programs that are interoperable with other Linux distributions.</para>
|
---|
| 158 | </listitem>
|
---|
| 159 | </varlistentry>
|
---|
| 160 |
|
---|
| 161 | <varlistentry>
|
---|
| 162 | <term><parameter>--enable-languages=c,c++</parameter></term>
|
---|
| 163 | <listitem>
|
---|
| 164 | <para>This option ensures that both the C and C++ compilers are
|
---|
| 165 | built.</para>
|
---|
| 166 | </listitem>
|
---|
| 167 | </varlistentry>
|
---|
| 168 |
|
---|
| 169 | <varlistentry>
|
---|
| 170 | <term><parameter>--disable-libstdcxx-pch</parameter></term>
|
---|
| 171 | <listitem>
|
---|
| 172 | <para>Do not build the pre-compiled header (PCH) for
|
---|
| 173 | <filename class="libraryfile">libstdc++</filename>. It takes up a
|
---|
| 174 | lot of space, and we have no use for it.</para>
|
---|
| 175 | </listitem>
|
---|
| 176 | </varlistentry>
|
---|
| 177 |
|
---|
| 178 | </variablelist>
|
---|
| 179 |
|
---|
| 180 | <para>Compile the package:</para>
|
---|
[73aedd1d] | 181 |
|
---|
| 182 | <screen><userinput>make</userinput></screen>
|
---|
| 183 |
|
---|
[d096eb1] | 184 | <para>There is no need to use the <parameter>bootstrap</parameter> target
|
---|
| 185 | now because the compiler being used to compile this GCC was built from
|
---|
| 186 | the exact same version of the GCC sources used earlier.</para>
|
---|
[81fd230] | 187 |
|
---|
[d096eb1] | 188 | <para>Compilation is now complete. As previously mentioned, running the test
|
---|
| 189 | suites for the temporary tools compiled in this chapter is not mandatory.
|
---|
| 190 | To run the GCC test suite anyway, use the following command:</para>
|
---|
[3d36131c] | 191 |
|
---|
[73aedd1d] | 192 | <screen><userinput>make -k check</userinput></screen>
|
---|
| 193 |
|
---|
[d096eb1] | 194 | <para>The <parameter>-k</parameter> flag is used to make the test suite run
|
---|
| 195 | through to completion and not stop at the first failure. The GCC test
|
---|
| 196 | suite is very comprehensive and is almost guaranteed to generate a few
|
---|
| 197 | failures. To receive a summary of the test suite results, run:</para>
|
---|
| 198 |
|
---|
[673b0d8] | 199 | <screen><userinput>../gcc-&gcc-version;/contrib/test_summary</userinput></screen>
|
---|
[e8692c5e] | 200 |
|
---|
[d096eb1] | 201 | <para>For only the summaries, pipe the output through
|
---|
| 202 | <userinput>grep -A7 Summ</userinput>.</para>
|
---|
[73aedd1d] | 203 |
|
---|
[d096eb1] | 204 | <para>Results can be compared with those located at <ulink
|
---|
| 205 | url="&test-results;"/>.</para>
|
---|
[81fd230] | 206 |
|
---|
[d096eb1] | 207 | <para>A few unexpected failures cannot always be avoided. The GCC developers
|
---|
| 208 | are usually aware of these issues, but have not resolved them yet. In
|
---|
| 209 | particular, the <filename class="libraryfile">libmudflap</filename> tests
|
---|
| 210 | are known be particularly problematic as a result of a bug in GCC
|
---|
| 211 | (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>).
|
---|
| 212 | Unless the test results are vastly different from those at the above URL,
|
---|
| 213 | it is safe to continue.</para>
|
---|
[ede9b9b] | 214 |
|
---|
[d096eb1] | 215 | <para>Install the package:</para>
|
---|
[73aedd1d] | 216 |
|
---|
| 217 | <screen><userinput>make install</userinput></screen>
|
---|
| 218 |
|
---|
[d096eb1] | 219 | <note>
|
---|
| 220 | <para>At this point it is strongly recommended to repeat the sanity
|
---|
| 221 | check we performed earlier in this chapter. Refer back to <xref
|
---|
| 222 | linkend="ch-tools-adjusting" role=","/> and repeat the test compilation.
|
---|
| 223 | If the result is wrong, the most likely reason is that the GCC Specs
|
---|
| 224 | patch was not properly applied.</para>
|
---|
| 225 | </note>
|
---|
[73aedd1d] | 226 |
|
---|
[d096eb1] | 227 | </sect2>
|
---|
[bc82645e] | 228 |
|
---|
[d096eb1] | 229 | <sect2 role="content">
|
---|
| 230 | <title/>
|
---|
[81fd230] | 231 |
|
---|
[d096eb1] | 232 | <para>Details on this package are located in
|
---|
| 233 | <xref linkend="contents-gcc" role="."/></para>
|
---|
[81fd230] | 234 |
|
---|
[d096eb1] | 235 | </sect2>
|
---|
| 236 |
|
---|
| 237 | </sect1>
|
---|