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