1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-tools-gcc-pass2" role="wrap">
|
---|
9 | <?dbhtml filename="gcc-pass2.html"?>
|
---|
10 |
|
---|
11 | <sect1info condition="script">
|
---|
12 | <productname>gcc</productname>
|
---|
13 | <productnumber>&gcc-version;</productnumber>
|
---|
14 | <address>&gcc-url;</address>
|
---|
15 | </sect1info>
|
---|
16 |
|
---|
17 | <title>GCC-&gcc-version; - Pass 2</title>
|
---|
18 |
|
---|
19 | <indexterm zone="ch-tools-gcc-pass2">
|
---|
20 | <primary sortas="a-GCC">GCC</primary>
|
---|
21 | <secondary>tools, pass 2</secondary>
|
---|
22 | </indexterm>
|
---|
23 |
|
---|
24 | <sect2 role="package">
|
---|
25 | <title/>
|
---|
26 |
|
---|
27 | <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
---|
28 | href="../chapter06/gcc.xml"
|
---|
29 | xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
|
---|
30 |
|
---|
31 | <segmentedlist>
|
---|
32 | <segtitle>&buildtime;</segtitle>
|
---|
33 | <segtitle>&diskspace;</segtitle>
|
---|
34 |
|
---|
35 | <seglistitem>
|
---|
36 | <seg>&gcc-ch5p2-sbu;</seg>
|
---|
37 | <seg>&gcc-ch5p2-du;</seg>
|
---|
38 | </seglistitem>
|
---|
39 | </segmentedlist>
|
---|
40 |
|
---|
41 | </sect2>
|
---|
42 |
|
---|
43 | <sect2 role="installation">
|
---|
44 | <title>Installation of GCC</title>
|
---|
45 |
|
---|
46 | <para>Our first build of GCC has installed a couple of internal system
|
---|
47 | headers. Normally one of them, <filename>limits.h</filename>, will in turn
|
---|
48 | include the corresponding system <filename>limits.h</filename> header, in
|
---|
49 | this case, <filename>/tools/include/limits.h</filename>. However, at the
|
---|
50 | time of the first build of gcc <filename>/tools/include/limits.h</filename>
|
---|
51 | did not exist, so the internal header that GCC installed is a partial,
|
---|
52 | self-contained file and does not include the extended features of the
|
---|
53 | system header. This was adequate for building the temporary libc, but this
|
---|
54 | build of GCC now requires the full internal header. Create a full version
|
---|
55 | of the internal header using a command that is identical to what the GCC
|
---|
56 | build system does in normal circumstances:</para>
|
---|
57 |
|
---|
58 | <screen><userinput remap="pre">cat gcc/limitx.h gcc/glimits.h gcc/limity.h > \
|
---|
59 | `dirname $($LFS_TGT-gcc -print-libgcc-file-name)`/include-fixed/limits.h</userinput></screen>
|
---|
60 | <!--
|
---|
61 | <para>For x86 machines, the limited number of registers is a bottleneck
|
---|
62 | for the system. Free one up by not using a frame pointer that is not
|
---|
63 | needed:</para>
|
---|
64 |
|
---|
65 | <screen><userinput remap="pre">case `uname -m` in
|
---|
66 | i?86) sed -i 's/^T_CFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in ;;
|
---|
67 | esac</userinput></screen>
|
---|
68 | -->
|
---|
69 | <para>Once again, change the location of GCC's default dynamic linker to
|
---|
70 | use the one installed in <filename
|
---|
71 | class="directory">/tools</filename>.</para>
|
---|
72 |
|
---|
73 | <screen><userinput remap="pre">for file in \
|
---|
74 | $(find gcc/config -name linux64.h -o -name linux.h -o -name sysv4.h)
|
---|
75 | do
|
---|
76 | cp -uv $file{,.orig}
|
---|
77 | sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&@g' \
|
---|
78 | -e 's@/usr@/tools@g' $file.orig > $file
|
---|
79 | echo '
|
---|
80 | #undef STANDARD_STARTFILE_PREFIX_1
|
---|
81 | #undef STANDARD_STARTFILE_PREFIX_2
|
---|
82 | #define STANDARD_STARTFILE_PREFIX_1 "/tools/lib/"
|
---|
83 | #define STANDARD_STARTFILE_PREFIX_2 ""' >> $file
|
---|
84 | touch $file.orig
|
---|
85 | done</userinput></screen>
|
---|
86 |
|
---|
87 | <para>As in the first build of GCC it requires the GMP, MPFR and MPC
|
---|
88 | packages. Unpack the tarballs and move them into the required directory
|
---|
89 | names:</para>
|
---|
90 |
|
---|
91 | <screen><userinput remap="pre">tar -xf ../mpfr-&mpfr-version;.tar.xz
|
---|
92 | mv -v mpfr-&mpfr-version; mpfr
|
---|
93 | tar -xf ../gmp-&gmp-version;.tar.xz
|
---|
94 | mv -v gmp-&gmp-extracted-version; gmp
|
---|
95 | tar -xf ../mpc-&mpc-version;.tar.gz
|
---|
96 | mv -v mpc-&mpc-version; mpc</userinput></screen>
|
---|
97 |
|
---|
98 | <para>As in the first build of GCC, fix a problem identified upstream:</para>
|
---|
99 |
|
---|
100 | <screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&\& \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen>
|
---|
101 |
|
---|
102 | <para>Create a separate build directory again:</para>
|
---|
103 |
|
---|
104 | <screen><userinput remap="pre">mkdir -v ../gcc-build
|
---|
105 | cd ../gcc-build</userinput></screen>
|
---|
106 |
|
---|
107 | <para>Before starting to build GCC, remember to unset any environment
|
---|
108 | variables that override the default optimization flags.</para>
|
---|
109 |
|
---|
110 | <para>Now prepare GCC for compilation:</para>
|
---|
111 |
|
---|
112 | <screen><userinput remap="configure">CC=$LFS_TGT-gcc \
|
---|
113 | CXX=$LFS_TGT-g++ \
|
---|
114 | AR=$LFS_TGT-ar \
|
---|
115 | RANLIB=$LFS_TGT-ranlib \
|
---|
116 | ../gcc-&gcc-version;/configure \
|
---|
117 | --prefix=/tools \
|
---|
118 | --with-local-prefix=/tools \
|
---|
119 | --with-native-system-header-dir=/tools/include \
|
---|
120 | --enable-clocale=gnu \
|
---|
121 | --enable-shared \
|
---|
122 | --enable-threads=posix \
|
---|
123 | --enable-__cxa_atexit \
|
---|
124 | --enable-languages=c,c++ \
|
---|
125 | --disable-libstdcxx-pch \
|
---|
126 | --disable-multilib \
|
---|
127 | --disable-bootstrap \
|
---|
128 | --disable-libgomp</userinput></screen>
|
---|
129 |
|
---|
130 | <variablelist>
|
---|
131 | <title>The meaning of the new configure options:</title>
|
---|
132 |
|
---|
133 | <varlistentry>
|
---|
134 | <term><parameter>--enable-clocale=gnu</parameter></term>
|
---|
135 | <listitem>
|
---|
136 | <para>This option ensures the correct locale model is selected
|
---|
137 | for the C++ libraries under all circumstances. If the configure
|
---|
138 | script finds the <emphasis>de_DE</emphasis> locale installed,
|
---|
139 | it will select the correct gnu locale model. However, if the
|
---|
140 | <emphasis>de_DE</emphasis> locale is not installed, there is the
|
---|
141 | risk of building Application Binary Interface (ABI)-incompatible
|
---|
142 | C++ libraries because the incorrect generic locale model may be
|
---|
143 | selected.</para>
|
---|
144 | </listitem>
|
---|
145 | </varlistentry>
|
---|
146 |
|
---|
147 | <varlistentry>
|
---|
148 | <term><parameter>--enable-threads=posix</parameter></term>
|
---|
149 | <listitem>
|
---|
150 | <para>This enables C++ exception handling for multi-threaded code.</para>
|
---|
151 | </listitem>
|
---|
152 | </varlistentry>
|
---|
153 |
|
---|
154 | <varlistentry>
|
---|
155 | <term><parameter>--enable-__cxa_atexit</parameter></term>
|
---|
156 | <listitem>
|
---|
157 | <para>This option allows use of <function>__cxa_atexit</function>,
|
---|
158 | rather than <function>atexit</function>, to register C++ destructors
|
---|
159 | for local statics and global objects. This option is essential for
|
---|
160 | fully standards-compliant handling of destructors. It also affects
|
---|
161 | the C++ ABI, and therefore results in C++ shared libraries and C++
|
---|
162 | programs that are interoperable with other Linux distributions.</para>
|
---|
163 | </listitem>
|
---|
164 | </varlistentry>
|
---|
165 |
|
---|
166 | <varlistentry>
|
---|
167 | <term><parameter>--enable-languages=c,c++</parameter></term>
|
---|
168 | <listitem>
|
---|
169 | <para>This option ensures that both the C and C++ compilers are
|
---|
170 | built.</para>
|
---|
171 | </listitem>
|
---|
172 | </varlistentry>
|
---|
173 |
|
---|
174 | <varlistentry>
|
---|
175 | <term><parameter>--disable-libstdcxx-pch</parameter></term>
|
---|
176 | <listitem>
|
---|
177 | <para>Do not build the pre-compiled header (PCH) for
|
---|
178 | <filename class="libraryfile">libstdc++</filename>. It takes up a
|
---|
179 | lot of space, and we have no use for it.</para>
|
---|
180 | </listitem>
|
---|
181 | </varlistentry>
|
---|
182 |
|
---|
183 | <varlistentry>
|
---|
184 | <term><parameter>--disable-bootstrap</parameter></term>
|
---|
185 | <listitem>
|
---|
186 | <para>For native builds of GCC, the default is to do a "bootstrap"
|
---|
187 | build. This does not just compile GCC, but compiles it several times.
|
---|
188 | It uses the programs compiled in a first round to compile itself a
|
---|
189 | second time, and then again a third time. The second and third
|
---|
190 | iterations are compared to make sure it can reproduce itself
|
---|
191 | flawlessly. This also implies that it was compiled correctly.
|
---|
192 | However, the LFS build method should provide a solid compiler
|
---|
193 | without the need to bootstrap each time.</para>
|
---|
194 | </listitem>
|
---|
195 | </varlistentry>
|
---|
196 |
|
---|
197 | </variablelist>
|
---|
198 |
|
---|
199 | <para>Compile the package:</para>
|
---|
200 |
|
---|
201 | <screen><userinput remap="make">make</userinput></screen>
|
---|
202 |
|
---|
203 | <para>Install the package:</para>
|
---|
204 |
|
---|
205 | <screen><userinput remap="install">make install</userinput></screen>
|
---|
206 |
|
---|
207 | <para>As a finishing touch, create a symlink. Many programs and scripts
|
---|
208 | run <command>cc</command> instead of <command>gcc</command>, which is
|
---|
209 | used to keep programs generic and therefore usable on all kinds of UNIX
|
---|
210 | systems where the GNU C compiler is not always installed. Running
|
---|
211 | <command>cc</command> leaves the system administrator free to decide
|
---|
212 | which C compiler to install:</para>
|
---|
213 |
|
---|
214 | <screen><userinput remap="install">ln -sv gcc /tools/bin/cc</userinput></screen>
|
---|
215 |
|
---|
216 | <caution>
|
---|
217 | <para>At this point, it is imperative to stop and ensure that the basic
|
---|
218 | functions (compiling and linking) of the new toolchain are working as
|
---|
219 | expected. To perform a sanity check, run the following commands:</para>
|
---|
220 |
|
---|
221 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
222 | cc dummy.c
|
---|
223 | readelf -l a.out | grep ': /tools'</userinput></screen>
|
---|
224 |
|
---|
225 | <para>If everything is working correctly, there should be no errors,
|
---|
226 | and the output of the last command will be of the form:</para>
|
---|
227 |
|
---|
228 | <screen><computeroutput>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</computeroutput></screen>
|
---|
229 |
|
---|
230 | <para>Note that <filename class="directory">/tools/lib</filename>, or
|
---|
231 | <filename class="directory">/tools/lib64</filename> for 64-bit machines
|
---|
232 | appears as the prefix of the dynamic linker.</para>
|
---|
233 |
|
---|
234 | <para>If the output is not shown as above or there was no output at all,
|
---|
235 | then something is wrong. Investigate and retrace the steps to find out
|
---|
236 | where the problem is and correct it. This issue must be resolved before
|
---|
237 | continuing on. First, perform the sanity check again, using
|
---|
238 | <command>gcc</command> instead of <command>cc</command>. If this works,
|
---|
239 | then the <filename class="symlink">/tools/bin/cc</filename> symlink is
|
---|
240 | missing. Install the symlink as per above.
|
---|
241 | Next, ensure that the <envar>PATH</envar> is correct. This
|
---|
242 | can be checked by running <command>echo $PATH</command> and verifying that
|
---|
243 | <filename class="directory">/tools/bin</filename> is at the head of the
|
---|
244 | list. If the <envar>PATH</envar> is wrong it could mean that you are not
|
---|
245 | logged in as user <systemitem class="username">lfs</systemitem> or that
|
---|
246 | something went wrong back in <xref linkend="ch-tools-settingenviron"
|
---|
247 | role="."/></para>
|
---|
248 |
|
---|
249 | <para>Once all is well, clean up the test files:</para>
|
---|
250 |
|
---|
251 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
---|
252 |
|
---|
253 | </caution>
|
---|
254 |
|
---|
255 | </sect2>
|
---|
256 |
|
---|
257 | <sect2 role="content">
|
---|
258 | <title/>
|
---|
259 |
|
---|
260 | <para>Details on this package are located in
|
---|
261 | <xref linkend="contents-gcc" role="."/></para>
|
---|
262 |
|
---|
263 | </sect2>
|
---|
264 |
|
---|
265 | </sect1>
|
---|