1 | <sect2><title> </title><para> </para></sect2>
|
---|
2 |
|
---|
3 | <sect2>
|
---|
4 | <title>Installation of GCC</title>
|
---|
5 |
|
---|
6 | <note><para>The test suite for GCC in this section is considered
|
---|
7 | <emphasis>critical</emphasis>. Our advice is to not skip it under any
|
---|
8 | circumstance.</para></note>
|
---|
9 |
|
---|
10 | <para>This package is known to behave badly when you have changed its
|
---|
11 | default optimization flags (including the -march and -mcpu options).
|
---|
12 | Therefore, if you have defined any environment variables that override
|
---|
13 | default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
|
---|
14 | or modifying them when building GCC.</para>
|
---|
15 |
|
---|
16 | <para>This time we will build both the C and the C++ compiler, so you'll have
|
---|
17 | to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
|
---|
18 | will unfold into the same directory. You should likewise extract the
|
---|
19 | GCC-testsuite package. The full GCC package contains even more
|
---|
20 | compilers. Instructions for building these can be found at
|
---|
21 | <ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para>
|
---|
22 |
|
---|
23 | <screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch;
|
---|
24 | patch -Np1 -i ../&gcc-suppress-libiberty-patch;</userinput></screen>
|
---|
25 |
|
---|
26 | <para>The second patch here suppresses the installation of libiberty from GCC,
|
---|
27 | as we will use the one provided by binutils instead. Be careful
|
---|
28 | <emphasis>not</emphasis> to apply the GCC specs patch from Chapter 5
|
---|
29 | here.</para>
|
---|
30 |
|
---|
31 | <para>The GCC documentation recommends building GCC outside of the source
|
---|
32 | directory in a dedicated build directory:</para>
|
---|
33 |
|
---|
34 | <screen><userinput>mkdir ../gcc-build
|
---|
35 | cd ../gcc-build</userinput></screen>
|
---|
36 |
|
---|
37 | <para>Now prepare GCC for compilation:</para>
|
---|
38 |
|
---|
39 | <screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
|
---|
40 | --enable-shared --enable-threads=posix \
|
---|
41 | --enable-__cxa_atexit --enable-clocale=gnu \
|
---|
42 | --enable-languages=c,c++</userinput></screen>
|
---|
43 |
|
---|
44 | <para>Compile the package:</para>
|
---|
45 |
|
---|
46 | <screen><userinput>make</userinput></screen>
|
---|
47 |
|
---|
48 | <para>Test the results, but don't stop at errors (you'll remember the few
|
---|
49 | known ones):</para>
|
---|
50 |
|
---|
51 | <screen><userinput>make -k check</userinput></screen>
|
---|
52 |
|
---|
53 | <para>The test suite notes from <xref linkend="ch05-gcc-pass2"/> are still very
|
---|
54 | much appropriate here. Be sure to refer back there should you have any
|
---|
55 | doubts.</para>
|
---|
56 |
|
---|
57 | <para>And install the package:</para>
|
---|
58 |
|
---|
59 | <screen><userinput>make install</userinput></screen>
|
---|
60 |
|
---|
61 | <para>Some packages expect the C PreProcessor to be installed in the
|
---|
62 | <filename>/lib</filename> directory.
|
---|
63 | To honor those packages, create this symlink:</para>
|
---|
64 |
|
---|
65 | <screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
|
---|
66 |
|
---|
67 | <para>Many packages use the name <userinput>cc</userinput> to call the C
|
---|
68 | compiler. To satisfy those packages, create a symlink:</para>
|
---|
69 |
|
---|
70 | <screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen>
|
---|
71 |
|
---|
72 | <note><para>At this point it is strongly recommended to repeat the sanity check
|
---|
73 | we performed earlier in this chapter. Refer back to
|
---|
74 | <xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results
|
---|
75 | are wrong, then most likely you erroneously applied the GCC Specs patch from
|
---|
76 | Chapter 5.</para></note>
|
---|
77 |
|
---|
78 | </sect2>
|
---|