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 | <!ENTITY gcc-download-http "&gnu-http;/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.xz">
|
---|
8 | <!ENTITY gcc-download-ftp "&gnu-ftp;/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.xz">
|
---|
9 | <!ENTITY gcc-md5sum "31c86f2ced76acac66992eeedce2fce2">
|
---|
10 | <!ENTITY gcc-size "77 MB">
|
---|
11 | <!ENTITY gcc-buildsize "8.0 GB (2.4 GB installed with all listed languages; add 1.0 GB for tests)">
|
---|
12 | <!-- For me the SBU values are a bit faster on haswell, but much slower on ryzen 3400G,
|
---|
13 | so keeping these existing values as an approximation - ken -->
|
---|
14 | <!ENTITY gcc-time "26 SBU (add 56 SBU for tests; both with parallelism=4)">
|
---|
15 | ]>
|
---|
16 |
|
---|
17 | <sect1 id="gcc" xreflabel="GCC-&gcc-version;">
|
---|
18 | <?dbhtml filename="gcc.html" ?>
|
---|
19 |
|
---|
20 | <sect1info>
|
---|
21 | <date>$Date$</date>
|
---|
22 | </sect1info>
|
---|
23 |
|
---|
24 | <title>GCC-&gcc-version;</title>
|
---|
25 |
|
---|
26 | <indexterm zone="gcc">
|
---|
27 | <primary sortas="a-gcc-5-0">GCC-&gcc-version;</primary>
|
---|
28 | </indexterm>
|
---|
29 |
|
---|
30 | <sect2 role="package">
|
---|
31 | <title>Introduction to GCC</title>
|
---|
32 |
|
---|
33 | <para>
|
---|
34 | The <application>GCC</application> package contains the GNU Compiler
|
---|
35 | Collection. This page describes the installation of compilers for the
|
---|
36 | following languages: C, C++, D, Fortran, Objective C, Objective C++, and Go.
|
---|
37 | <!--One additional language, Ada, is available in the collection. It has
|
---|
38 | a binary bootstrap requirement for the first installation, so it is
|
---|
39 | described on a separate page (<xref linkend="gcc-ada"/>) but can be added
|
---|
40 | here if you are performing a rebuild or upgrade. Since C and C++ are
|
---|
41 | installed in LFS, this page is either for upgrading C and C++, or for
|
---|
42 | installing additional compilers.-->
|
---|
43 | </para>
|
---|
44 |
|
---|
45 | &lfs111_checked;
|
---|
46 |
|
---|
47 | <caution>
|
---|
48 | <para>
|
---|
49 | If you are upgrading <application>GCC</application> from any other
|
---|
50 | version prior to &gcc-version;, then you must be careful compiling 3rd
|
---|
51 | party kernel modules. You should ensure that the kernel and all its
|
---|
52 | native modules are also compiled using the same version of
|
---|
53 | <application>GCC</application> that you use to build the 3rd party module.
|
---|
54 | This issue does not affect native kernel (and kernel modules) updates,
|
---|
55 | as the instructions below are a complete reinstallation of
|
---|
56 | <application>GCC</application>. If you have existing 3rd party modules
|
---|
57 | installed, ensure they are recompiled using the updated version of
|
---|
58 | <application>GCC</application>. As always, never update the kernel
|
---|
59 | headers from the ones used when <application>Glibc</application> was
|
---|
60 | compiled during LFS.
|
---|
61 | </para>
|
---|
62 |
|
---|
63 | <para>
|
---|
64 | Some system headers need to be fixed to be used with GCC. This is done
|
---|
65 | during the installation of GCC, and the <quote>fixed</quote> headers
|
---|
66 | are installed in <filename class="directory">
|
---|
67 | /usr/lib/gcc/<machine triplet>/<GCC version>/include-fixed
|
---|
68 | </filename>. This is harmless if GCC is built during the LFS stage. But
|
---|
69 | if you reinstall GCC in BLFS, some of the BLFS packages may be
|
---|
70 | <quote>fixed</quote>. If one of those packages is reinstalled
|
---|
71 | afterwards, the <quote>fixed</quote> headers are not updated, which may
|
---|
72 | lead to version mismatches. In case that happens, the
|
---|
73 | <quote>fixed</quote> headers must be updated by running (as
|
---|
74 | <systemitem class="username">root</systemitem>):
|
---|
75 | <command>
|
---|
76 | /usr/libexec/gcc/x86_64-pc-linux-gnu/&gcc-version;/install-tools/mkheaders
|
---|
77 | </command>. The machine triplet may be different on a 32bit system.
|
---|
78 | </para>
|
---|
79 | </caution>
|
---|
80 |
|
---|
81 | <bridgehead renderas="sect3">Package Information</bridgehead>
|
---|
82 | <itemizedlist spacing="compact">
|
---|
83 | <listitem>
|
---|
84 | <para>
|
---|
85 | Download (HTTP): <ulink url="&gcc-download-http;"/>
|
---|
86 | </para>
|
---|
87 | </listitem>
|
---|
88 | <listitem>
|
---|
89 | <para>
|
---|
90 | Download (FTP): <ulink url="&gcc-download-ftp;"/>
|
---|
91 | </para>
|
---|
92 | </listitem>
|
---|
93 | <listitem>
|
---|
94 | <para>
|
---|
95 | Download MD5 sum: &gcc-md5sum;
|
---|
96 | </para>
|
---|
97 | </listitem>
|
---|
98 | <listitem>
|
---|
99 | <para>
|
---|
100 | Download size: &gcc-size;
|
---|
101 | </para>
|
---|
102 | </listitem>
|
---|
103 | <listitem>
|
---|
104 | <para>
|
---|
105 | Estimated disk space required: &gcc-buildsize;
|
---|
106 | </para>
|
---|
107 | </listitem>
|
---|
108 | <listitem>
|
---|
109 | <para>
|
---|
110 | Estimated build time: &gcc-time;
|
---|
111 | </para>
|
---|
112 | </listitem>
|
---|
113 | </itemizedlist>
|
---|
114 |
|
---|
115 | <bridgehead renderas="sect3">GCC Dependencies</bridgehead>
|
---|
116 | <!--
|
---|
117 | <bridgehead renderas="sect4">Recommended</bridgehead>
|
---|
118 | <para role="recommended">
|
---|
119 | <xref linkend="dejagnu"/>, for tests
|
---|
120 | </para>
|
---|
121 | -->
|
---|
122 | <bridgehead renderas="sect4">Optional</bridgehead>
|
---|
123 | <para role="optional">
|
---|
124 | <xref linkend="gdb"/>,
|
---|
125 | <xref linkend="valgrind"/> (for tests), and
|
---|
126 | <ulink url="https://repo.or.cz/isl.git">ISL</ulink> (to enable graphite optimization)
|
---|
127 | </para>
|
---|
128 |
|
---|
129 | <para condition="html" role="usernotes">
|
---|
130 | User Notes: <ulink url="&blfs-wiki;/gcc"/>
|
---|
131 | </para>
|
---|
132 |
|
---|
133 | </sect2>
|
---|
134 |
|
---|
135 | <sect2 role="installation">
|
---|
136 | <title>Installation of GCC</title>
|
---|
137 |
|
---|
138 | <important>
|
---|
139 | <para>
|
---|
140 | Even if you specify only languages other than C and C++ to the
|
---|
141 | <command>./configure</command> command below, the
|
---|
142 | installation process will overwrite your existing
|
---|
143 | <application>GCC</application> C and C++ compilers and libraries.
|
---|
144 | <!--Having the <application>Tcl</application>,
|
---|
145 | <application>Expect</application> and <application>DejaGnu</application>
|
---|
146 | packages installed before beginning the build is highly recommended so
|
---|
147 | you can run the full suite of tests.-->
|
---|
148 | Running the full suite of tests is recommended.
|
---|
149 | </para>
|
---|
150 |
|
---|
151 | <para>
|
---|
152 | Do not continue with the <command>make install</command> command
|
---|
153 | until you are confident the build was successful. You can compare your
|
---|
154 | test results with those found at <ulink
|
---|
155 | url="https://gcc.gnu.org/ml/gcc-testresults/"/>. You may also want to
|
---|
156 | refer to the information found in the <application>GCC</application>
|
---|
157 | section of Chapter 8 in the LFS book (<ulink
|
---|
158 | url="&lfs-root;/chapter08/gcc.html"/>).
|
---|
159 | </para>
|
---|
160 | </important>
|
---|
161 |
|
---|
162 | <para>
|
---|
163 | The instructions below are intentionally performing a
|
---|
164 | <quote>bootstrap</quote> process. Bootstrapping is needed for robustness
|
---|
165 | and is highly recommended when upgrading the compilers version. To disable
|
---|
166 | bootstrap anyways, add <parameter>--disable-bootstrap</parameter> to the
|
---|
167 | <command>./configure</command> options below.
|
---|
168 | </para>
|
---|
169 |
|
---|
170 | <para>
|
---|
171 | As in LFS fix an issue breaking libasan.a identified upstream:
|
---|
172 | </para>
|
---|
173 |
|
---|
174 | <screen><userinput>sed -e '/static.*SIGSTKSZ/d' \
|
---|
175 | -e 's/return kAltStackSize/return SIGSTKSZ * 4/' \
|
---|
176 | -i libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp</userinput></screen>
|
---|
177 |
|
---|
178 | <para>
|
---|
179 | Install <application>GCC</application> by running the following commands:
|
---|
180 | </para>
|
---|
181 |
|
---|
182 | <screen><userinput>case $(uname -m) in
|
---|
183 | x86_64)
|
---|
184 | sed -i.orig '/m64=/s/lib64/lib/' gcc/config/i386/t-linux64
|
---|
185 | ;;
|
---|
186 | esac
|
---|
187 |
|
---|
188 | mkdir build &&
|
---|
189 | cd build &&
|
---|
190 |
|
---|
191 | ../configure \
|
---|
192 | --prefix=/usr \
|
---|
193 | --disable-multilib \
|
---|
194 | --with-system-zlib \
|
---|
195 | --enable-languages=c,c++,d,fortran,go,objc,obj-c++ &&
|
---|
196 | make</userinput></screen>
|
---|
197 |
|
---|
198 | <para>
|
---|
199 | If you have installed additional packages such as
|
---|
200 | <application>Valgrind</application> and <application>GDB</application>,
|
---|
201 | the <application>GCC</application> part of the testsuite will run more
|
---|
202 | tests than in LFS. Some of those will report FAIL and others XPASS
|
---|
203 | (pass when expected to FAIL). As of gcc-11.1.0, about 90 FAIL occur
|
---|
204 | in the <quote>guality</quote> suite, as well as miscellaneous failures
|
---|
205 | throughout the rest of the test suite. If all the compilers above are
|
---|
206 | built, there will be around 102 unexpected failures out of over
|
---|
207 | 481,000 tests. To run the tests, issue:
|
---|
208 | </para>
|
---|
209 |
|
---|
210 | <screen><userinput>ulimit -s 32768 &&
|
---|
211 | make -k check</userinput></screen>
|
---|
212 | <!-- The command above may error out, so using && may prevent the summary
|
---|
213 | to be run. -->
|
---|
214 |
|
---|
215 | <para>
|
---|
216 | The tests are very long, and the results may be hard to find in the
|
---|
217 | logs, specially if you use parallel jobs with make. You can get a summary
|
---|
218 | of the tests with:
|
---|
219 | </para>
|
---|
220 |
|
---|
221 | <screen><userinput>../contrib/test_summary</userinput></screen>
|
---|
222 |
|
---|
223 | <para>A few tests, less than 20 out of about 450,000, will fail, but unless
|
---|
224 | the failures are excessive, they can be ignored.</para>
|
---|
225 |
|
---|
226 | <para>
|
---|
227 | Now, as the <systemitem class="username">root</systemitem> user:
|
---|
228 | </para>
|
---|
229 |
|
---|
230 | <screen role="root"><userinput>make install &&
|
---|
231 |
|
---|
232 | mkdir -pv /usr/share/gdb/auto-load/usr/lib &&
|
---|
233 | mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib &&
|
---|
234 |
|
---|
235 | chown -v -R root:root \
|
---|
236 | /usr/lib/gcc/*linux-gnu/&gcc-version;/include{,-fixed}
|
---|
237 |
|
---|
238 | rm -rf /usr/lib/gcc/$(gcc -dumpmachine)/&gcc-version;/include-fixed/bits/</userinput></screen>
|
---|
239 |
|
---|
240 | <para>
|
---|
241 | Some packages expect to find the C preprocessor in
|
---|
242 | <filename class="directory">/lib</filename> or may refer to the C compiler
|
---|
243 | under the name <command>cc</command>. The following symbolic links are not
|
---|
244 | needed if you have followed the LFS instructions, since they
|
---|
245 | have been already created. If you do not have them on your system, issue
|
---|
246 | as the <systemitem class="username">root</systemitem> user:
|
---|
247 | </para>
|
---|
248 |
|
---|
249 | <screen role="root"><userinput>ln -v -sf ../usr/bin/cpp /lib &&
|
---|
250 | ln -v -sf gcc /usr/bin/cc &&
|
---|
251 | install -v -dm755 /usr/lib/bfd-plugins &&
|
---|
252 | ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so /usr/lib/bfd-plugins/</userinput></screen>
|
---|
253 |
|
---|
254 | </sect2>
|
---|
255 |
|
---|
256 | <sect2 role="commands">
|
---|
257 | <title>Command Explanations</title>
|
---|
258 |
|
---|
259 | <para>
|
---|
260 | <command>mkdir build; cd build</command>: The
|
---|
261 | <application>GCC</application> documentation recommends
|
---|
262 | building the package in a dedicated build directory.
|
---|
263 | </para>
|
---|
264 |
|
---|
265 | <para>
|
---|
266 | <parameter>--disable-multilib</parameter>: This parameter ensures
|
---|
267 | that files are created for the specific architecture of your computer.
|
---|
268 | </para>
|
---|
269 |
|
---|
270 | <para>
|
---|
271 | <parameter>--with-system-zlib</parameter>: Uses the system
|
---|
272 | <application>zlib</application> instead of the bundled one.
|
---|
273 | <application>zlib</application> is used for compressing
|
---|
274 | and uncompressing <application>GCC</application>'s intermediate
|
---|
275 | language in LTO (Link Time Optimization) object files.
|
---|
276 | </para>
|
---|
277 |
|
---|
278 | <para>
|
---|
279 | <parameter>--enable-languages=c,c++,d,fortran,go,objc,obj-c++</parameter>:
|
---|
280 | This command identifies which languages to build. You may modify
|
---|
281 | this command to remove undesired languages. Three other languages can be
|
---|
282 | added, including ADA, BRIG (add
|
---|
283 | <parameter>brig</parameter> to the list of enabled languages), a binary
|
---|
284 | format for HSAIL (Heterogeneous System Architecture Intermediate
|
---|
285 | Language), and JIT (add <parameter>jit</parameter> to the list of enabled
|
---|
286 | languages), a library which can be linked into interpreters that want to
|
---|
287 | generate machine code <quote>on the fly</quote> at run-time. They have not
|
---|
288 | been tested by the BLFS developers.
|
---|
289 | </para>
|
---|
290 | <!-- It's been three major versions now, and many years.
|
---|
291 | Commenting out unless needed somewhere. -renodr
|
---|
292 | <para>
|
---|
293 | <option>- -with-default-libstdcxx-abi=gcc4-compatible</option>: Use this
|
---|
294 | switch if you are upgrading from a <application>GCC</application>
|
---|
295 | version prior to 5.1.0, and you do not want to recompile all the
|
---|
296 | libraries written in C++.
|
---|
297 | </para>
|
---|
298 | -->
|
---|
299 |
|
---|
300 | <para>
|
---|
301 | <command>ulimit -s 32768</command>: This command prevents several
|
---|
302 | tests from running out of stack space.
|
---|
303 | </para>
|
---|
304 |
|
---|
305 | <para>
|
---|
306 | <command>make -k check</command>: This command runs the test suite
|
---|
307 | without stopping if any errors are encountered.
|
---|
308 | </para>
|
---|
309 |
|
---|
310 | <para>
|
---|
311 | <command>../contrib/test_summary</command>: This command will produce
|
---|
312 | a summary of the test suite results. You can append <command>| grep
|
---|
313 | -A7 Summ</command> to the command to produce an even more condensed
|
---|
314 | version of the summary. You may also wish to redirect the output
|
---|
315 | to a file for review and comparison later on.
|
---|
316 | </para>
|
---|
317 |
|
---|
318 | <para>
|
---|
319 | <command>mv -v /usr/lib/*gdb.py ...</command>: The installation
|
---|
320 | stage puts some files used by <application>gdb</application> under the
|
---|
321 | <filename class="directory">/usr/lib</filename> directory. This generates
|
---|
322 | spurious error messages when performing <command>ldconfig</command>. This
|
---|
323 | command moves the files to another location.
|
---|
324 | </para>
|
---|
325 |
|
---|
326 | <para>
|
---|
327 | <command>chown -v -R root:root /usr/lib/gcc/*linux-gnu/...</command>:
|
---|
328 | If the package is built by a user other than root, the ownership of the
|
---|
329 | installed <filename class="directory">include</filename> directory (and
|
---|
330 | its content) will be incorrect. This command changes the ownership to the
|
---|
331 | <systemitem class="username">root</systemitem> user and group.
|
---|
332 | </para>
|
---|
333 |
|
---|
334 | <para>
|
---|
335 | <command>rm -rf .../include-fixed/bits/</command>: Remove an erroneous
|
---|
336 | file in gcc added by the fixincludes process.
|
---|
337 | </para>
|
---|
338 |
|
---|
339 | </sect2>
|
---|
340 |
|
---|
341 | <sect2 role="content">
|
---|
342 | <title>Contents</title>
|
---|
343 |
|
---|
344 | <para>
|
---|
345 | Some program and library names and descriptions are not listed here,
|
---|
346 | but can be found at
|
---|
347 | <ulink url="&lfs-root;/chapter08/gcc.html#contents-gcc">LFS section
|
---|
348 | for GCC</ulink> as they were
|
---|
349 | initially installed during the building of LFS.
|
---|
350 | </para>
|
---|
351 |
|
---|
352 | <segmentedlist>
|
---|
353 | <segtitle>Installed Programs</segtitle>
|
---|
354 | <segtitle>Installed Libraries</segtitle>
|
---|
355 | <segtitle>Installed Directories</segtitle>
|
---|
356 |
|
---|
357 | <seglistitem>
|
---|
358 | <seg>
|
---|
359 | gccgo, gdc, gfortran, go, and gofmt, hard-linked to architecture
|
---|
360 | specific names
|
---|
361 | </seg>
|
---|
362 | <seg>
|
---|
363 | libgfortran.{so,a},
|
---|
364 | libgdruntime.{so,a}, libgphobos.{so,a}
|
---|
365 | libgo.{so,a}, libgobegin.a, libgolibbegin.a,
|
---|
366 | libobjc.{so,a}, and numerous other run-time libraries and executables
|
---|
367 | </seg>
|
---|
368 | <seg>
|
---|
369 | /usr/lib/go
|
---|
370 | </seg>
|
---|
371 | </seglistitem>
|
---|
372 | </segmentedlist>
|
---|
373 |
|
---|
374 | <variablelist>
|
---|
375 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
376 | <?dbfo list-presentation="list"?>
|
---|
377 | <?dbhtml list-presentation="table"?>
|
---|
378 |
|
---|
379 | <varlistentry id="gccgo">
|
---|
380 | <term><command>gccgo</command></term>
|
---|
381 | <listitem>
|
---|
382 | <para>
|
---|
383 | is a GCC-based compiler for the <application>Go</application>
|
---|
384 | language
|
---|
385 | </para>
|
---|
386 | <indexterm zone="gcc gccgo">
|
---|
387 | <primary sortas="b-gccgo">gccgo</primary>
|
---|
388 | </indexterm>
|
---|
389 | </listitem>
|
---|
390 | </varlistentry>
|
---|
391 |
|
---|
392 | <varlistentry id="go">
|
---|
393 | <term><command>go</command></term>
|
---|
394 | <listitem>
|
---|
395 | <para>
|
---|
396 | is a tool for managing <application>Go</application> source code
|
---|
397 | </para>
|
---|
398 | <indexterm zone="gcc go">
|
---|
399 | <primary sortas="b-go">go</primary>
|
---|
400 | </indexterm>
|
---|
401 | </listitem>
|
---|
402 | </varlistentry>
|
---|
403 |
|
---|
404 | <varlistentry id="gofmt">
|
---|
405 | <term><command>gofmt</command></term>
|
---|
406 | <listitem>
|
---|
407 | <para>
|
---|
408 | is a tool for formatting <application>Go</application> source code
|
---|
409 | </para>
|
---|
410 | <indexterm zone="gcc gofmt">
|
---|
411 | <primary sortas="b-gofmt">gofmt</primary>
|
---|
412 | </indexterm>
|
---|
413 | </listitem>
|
---|
414 | </varlistentry>
|
---|
415 |
|
---|
416 | <varlistentry id="gdc">
|
---|
417 | <term><command>gdc</command></term>
|
---|
418 | <listitem>
|
---|
419 | <para>
|
---|
420 | is a GCC-based compiler for the <application>D</application>
|
---|
421 | language
|
---|
422 | </para>
|
---|
423 | <indexterm zone="gcc gdc">
|
---|
424 | <primary sortas="b-gdc">gdc</primary>
|
---|
425 | </indexterm>
|
---|
426 | </listitem>
|
---|
427 | </varlistentry>
|
---|
428 |
|
---|
429 | <varlistentry id="gfortran">
|
---|
430 | <term><command>gfortran</command></term>
|
---|
431 | <listitem>
|
---|
432 | <para>
|
---|
433 | is a GCC-based compiler for the <application>Fortran</application>
|
---|
434 | language
|
---|
435 | </para>
|
---|
436 | <indexterm zone="gcc gfortran">
|
---|
437 | <primary sortas="b-gfortran">gfortran</primary>
|
---|
438 | </indexterm>
|
---|
439 | </listitem>
|
---|
440 | </varlistentry>
|
---|
441 |
|
---|
442 | </variablelist>
|
---|
443 |
|
---|
444 | </sect2>
|
---|
445 |
|
---|
446 | </sect1>
|
---|