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