source: chapter05/gcc-pass1-inst.xml@ 40f4d66

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 40f4d66 was 40f4d66, checked in by Greg Schafer <greg@…>, 21 years ago

Minor edits from Bill and Alex P. Thanks guys.

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

  • Property mode set to 100644
File size: 4.0 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
3<sect2>
4<title>Installation of GCC</title>
5
6<para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler
7for the moment.</para>
8
9<note><para>Even though GCC is an important toolchain package, we are not
10going to run the testsuite at this early stage. First, the testsuite framework
11is not yet in place and second, the programs from this first pass will soon be
12overwritten by those installed in the second pass.</para></note>
13
14<para>This package is known to behave badly when you have changed its
15default optimization flags (including the -march and -mcpu options).
16Therefore, if you have defined any environment variables that override
17default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
18or modifying them when building GCC.</para>
19
20<para>It is recommended by the GCC installation documentation to build
21GCC outside of the source directory in a dedicated directory:</para>
22
23<para><screen><userinput>mkdir ../gcc-build
24cd ../gcc-build</userinput></screen></para>
25
26<para>Prepare GCC to be compiled:</para>
27
28<para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
29&nbsp;&nbsp;&nbsp;&nbsp;--with-local-prefix=/tools \
30&nbsp;&nbsp;&nbsp;&nbsp;--disable-nls --enable-shared \
31&nbsp;&nbsp;&nbsp;&nbsp;--enable-languages=c</userinput></screen></para>
32
33<para>The meaning of the new configure options:</para>
34
35<itemizedlist>
36<listitem><para><userinput>--with-local-prefix=/tools</userinput>: The
37purpose of this switch is to remove <filename>/usr/local/include</filename>
38from <userinput>gcc</userinput>'s include search path. This is not absolutely
39essential; however, we want to try to minimize the influence of the host
40system, thus making this is a sensible thing to do.</para></listitem>
41
42<listitem><para><userinput>--enable-shared</userinput>: This switch may
43seem counter-intuitive at first. But using it allows the building of
44<filename>libgcc_s.so.1</filename> and <filename>libgcc_eh.a</filename>, and
45having <filename>libgcc_eh.a</filename> available ensures that the configure
46script for Glibc (the next package we compile) produces the proper results.
47Note that the <userinput>gcc</userinput> binaries will still be linked
48statically, as this is controlled by the <userinput>-static</userinput>
49value of BOOT_LDFLAGS further on.</para></listitem>
50
51<listitem><para><userinput>--enable-languages=c</userinput>: This option
52ensures that only the C compiler is built. The option is only needed when you
53have downloaded and unpacked the full GCC tarball.</para></listitem>
54</itemizedlist>
55
56<para>Continue with compiling the package:</para>
57
58<para><screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen></para>
59
60<para>The meaning of the make parameters:</para>
61
62<itemizedlist>
63<listitem><para><userinput>BOOT_LDFLAGS="-static"</userinput>: This tells
64GCC to link its programs statically.</para></listitem>
65
66<listitem><para><userinput>bootstrap</userinput>: This target doesn't just
67compile GCC, but compiles it several times. It uses the programs compiled in
68a first round to compile itself a second time, and then again a third time.
69It then compares these second and third compiles to make sure it can
70reproduce itself flawlessly, which most probably means that it was
71compiled correctly.</para></listitem>
72</itemizedlist>
73
74<para>And install the package:</para>
75
76<para><screen><userinput>make install</userinput></screen></para>
77
78<para>As a finishing touch we'll create the <filename
79class="symlink">/tools/bin/cc</filename> symlink. Many programs and
80scripts run <userinput>cc</userinput> instead of <userinput>gcc</userinput>,
81a thing meant to keep programs generic and therefore usable on all kinds of
82Unix systems. Not everybody has the GNU C compiler installed. Simply running
83<userinput>cc</userinput> leaves the system administrator free to decide what
84C compiler to install, as long as there's a symlink pointing to it:</para>
85
86<para><screen><userinput>ln -sf gcc /tools/bin/cc</userinput></screen></para>
87
88</sect2>
89
Note: See TracBrowser for help on using the repository browser.