source: chapter06/gcc-inst.xml@ 98b277a

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 98b277a was 8998cde, checked in by Jeremy Utley <jeremy@…>, 21 years ago

Added Greg's patch to GCC to suppress libiberty, and allowed binutils' libiberty to stay

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2767 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.4 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
3<sect2>
4<title>Installation of GCC</title>
5
6<para>This package is known to behave badly when you have changed its
7default optimization flags (including the -march and -mcpu options).
8Therefore, if you have defined any environment variables that override
9default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
10or modifying them when building GCC.</para>
11
12<para>This time we will build both the C and the C++ compiler, so you'll have
13to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
14will unfold into the same directory. You should likewise extract the
15GCC-testsuite package. The full GCC package contains even more
16compilers. Instructions for building these can be found at
17<ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para>
18
19<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-2.patch
20patch -Np1 -i ../gcc-3.3.1-suppress-libiberty.patch</userinput></screen></para>
21
22<para>The second patch here suppresses the installation of libiberty from GCC,
23as we will use the one provided by binutils instead.</para>
24
25<para>GCC's installation documentation recommends to build the package in a
26dedicated directory separate from the source tree. Create this build
27directory and go there:</para>
28
29<para><screen><userinput>mkdir ../gcc-build
30cd ../gcc-build</userinput></screen></para>
31
32<para>Now prepare GCC for compilation:</para>
33
34<para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
35&nbsp;&nbsp;&nbsp;&nbsp;--enable-shared --enable-threads=posix \
36&nbsp;&nbsp;&nbsp;&nbsp;--enable-__cxa_atexit --enable-clocale=gnu \
37&nbsp;&nbsp;&nbsp;&nbsp;--enable-languages=c,c++</userinput></screen></para>
38
39<para>The meaning of the new configure options:</para>
40
41<itemizedlist>
42<listitem><para><userinput>--enable-threads=posix</userinput>: This enables
43C++ exception handling for multi-threaded code.</para></listitem>
44
45<listitem><para><userinput>--enable-__cxa_atexit</userinput>: This option
46will result in C++ shared libraries and C++ programs that are interoperable
47with other Linux distributions.</para></listitem>
48
49<listitem><para><userinput>--enable-clocale=gnu</userinput>: There is a risk
50that some people will build ABI incompatible C++ libraries if they didn't
51install all of the glibc localedata. Using --enable-clocale=gnu ensures that
52the "right thing" is done in all cases. If you don't wish to use this option,
53then at least build the <emphasis>de_DE</emphasis> locale. When GCC finds
54this specific locale, then the correct locale mode (<emphasis>gnu</emphasis>)
55is implemented.</para></listitem>
56</itemizedlist>
57
58<para>Compile the package:</para>
59
60<para><screen><userinput>make</userinput></screen></para>
61
62<para>Test the results, but don't stop at errors (you'll remember the few
63known ones):</para>
64
65<para><screen><userinput>make -k check</userinput></screen></para>
66
67<para>And install the package:</para>
68
69<para><screen><userinput>make install</userinput></screen></para>
70
71<para>Some packages expect the C PreProcessor to be installed in the
72<filename>/lib</filename> directory.
73To honor those packages, create this symlink:</para>
74
75<para><screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen></para>
76
77<para>Many packages use the name <userinput>cc</userinput> to call the C
78compiler. To satisfy those packages, create a symlink:</para>
79
80<para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></para>
81
82</sect2>
Note: See TracBrowser for help on using the repository browser.