1 | <sect1 id="ch06-gcc" xreflabel="GCC">
|
---|
2 | <title>Installing GCC-&gcc-version;</title>
|
---|
3 | <?dbhtml filename="gcc.html" dir="chapter06"?>
|
---|
4 |
|
---|
5 | <para>The GCC package contains the GNU compiler collection, among them
|
---|
6 | the C and C++ compilers.</para>
|
---|
7 |
|
---|
8 | <screen>Estimated build time: &gcc-time;
|
---|
9 | Estimated required disk space: &gcc-compsize;</screen>
|
---|
10 |
|
---|
11 | <literallayout>Official download location for GCC (&gcc-version;):
|
---|
12 | <ulink url="ftp://ftp.gnu.org/pub/gnu/gcc/"/>
|
---|
13 | And for the GCC No-Fixincludes Patch:
|
---|
14 | <ulink url="&patches-root;&gcc-nofixincludes-patch;"/></literallayout>
|
---|
15 |
|
---|
16 | &aa-gcc-dep;
|
---|
17 |
|
---|
18 | <sect2><title> </title><para> </para></sect2>
|
---|
19 |
|
---|
20 | <sect2>
|
---|
21 | <title>Installation of GCC</title>
|
---|
22 |
|
---|
23 | <note><para>The test suite for GCC in this section is considered
|
---|
24 | <emphasis>critical</emphasis>. Our advice is to not skip it under any
|
---|
25 | circumstance.</para></note>
|
---|
26 |
|
---|
27 | <para>This package is known to behave badly when you have changed its
|
---|
28 | default optimization flags (including the -march and -mcpu options).
|
---|
29 | Therefore, if you have defined any environment variables that override
|
---|
30 | default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
|
---|
31 | or modifying them when building GCC.</para>
|
---|
32 |
|
---|
33 | <para>Unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
|
---|
34 | will unfold into the same directory. You should likewise extract the
|
---|
35 | GCC-testsuite package. The full GCC package contains even more
|
---|
36 | compilers. Instructions for building these can be found at
|
---|
37 | <ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para>
|
---|
38 |
|
---|
39 | <note><para>Be careful <emphasis role="strong">not</emphasis> to apply the GCC
|
---|
40 | Specs patch from Chapter 5 here.</para></note>
|
---|
41 |
|
---|
42 | <para>First apply the No-Fixincludes patch that we also used in the previous
|
---|
43 | chapter:</para>
|
---|
44 |
|
---|
45 | <screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch;</userinput></screen>
|
---|
46 |
|
---|
47 | <para>Now apply a sed substitution that will suppress the installation of
|
---|
48 | <filename>libiberty.a</filename>. We want to use the version of
|
---|
49 | <filename>libiberty.a</filename> provided by Binutils:</para>
|
---|
50 |
|
---|
51 | <screen><userinput>sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in</userinput></screen>
|
---|
52 |
|
---|
53 | <para>The GCC documentation recommends building GCC outside of the source
|
---|
54 | directory in a dedicated build directory:</para>
|
---|
55 |
|
---|
56 | <screen><userinput>mkdir ../gcc-build
|
---|
57 | cd ../gcc-build</userinput></screen>
|
---|
58 |
|
---|
59 | <para>Now prepare GCC for compilation:</para>
|
---|
60 |
|
---|
61 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
|
---|
62 | --enable-shared --enable-threads=posix \
|
---|
63 | --enable-__cxa_atexit --enable-clocale=gnu \
|
---|
64 | --enable-languages=c,c++</userinput></screen>
|
---|
65 |
|
---|
66 | <para>Compile the package:</para>
|
---|
67 |
|
---|
68 | <screen><userinput>make</userinput></screen>
|
---|
69 |
|
---|
70 | <para>Test the results, but don't stop at errors (you'll remember the few
|
---|
71 | known ones):</para>
|
---|
72 |
|
---|
73 | <screen><userinput>make -k check</userinput></screen>
|
---|
74 |
|
---|
75 | <para>The test suite notes from <xref linkend="ch05-gcc-pass2"/> are still very
|
---|
76 | much appropriate here. Be sure to refer back there should you have any
|
---|
77 | doubts.</para>
|
---|
78 |
|
---|
79 | <para>And install the package:</para>
|
---|
80 |
|
---|
81 | <screen><userinput>make install</userinput></screen>
|
---|
82 |
|
---|
83 | <para>Some packages expect the C PreProcessor to be installed in the
|
---|
84 | <filename>/lib</filename> directory.
|
---|
85 | To honor those packages, create this symlink:</para>
|
---|
86 |
|
---|
87 | <screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
|
---|
88 |
|
---|
89 | <para>Many packages use the name <userinput>cc</userinput> to call the C
|
---|
90 | compiler. To satisfy those packages, create a symlink:</para>
|
---|
91 |
|
---|
92 | <screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen>
|
---|
93 |
|
---|
94 | <note><para>At this point it is strongly recommended to repeat the sanity check
|
---|
95 | we performed earlier in this chapter. Refer back to
|
---|
96 | <xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results
|
---|
97 | are wrong, then most likely you erroneously applied the GCC Specs patch from
|
---|
98 | Chapter 5.</para></note>
|
---|
99 |
|
---|
100 | </sect2>
|
---|
101 |
|
---|
102 | &aa-gcc-shortdesc;
|
---|
103 | &aa-gcc-desc;
|
---|
104 |
|
---|
105 | </sect1>
|
---|
106 |
|
---|