source: general/prog/gcc.xml@ 3026cde

11.0 lazarus qt5new trunk
Last change on this file since 3026cde was 3026cde, checked in by Thomas Trepl (Moody) <thomas@…>, 4 months ago

Fix some typos

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