Ignore:
Timestamp:
11/01/2003 10:31:50 PM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
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
Children:
49f4dd5
Parents:
0b400add
Message:

Merging caption and installation sections for all packages in chapters 5 and 6.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/gcc-pass1.xml

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