Ignore:
Timestamp:
02/19/2005 10:16:42 PM (19 years ago)
Author:
Gerard Beekmans <gerard@…>
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.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, 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:
3d31fc4
Parents:
2f9131f
Message:

Trunk is now identical to Testing

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/gcc-pass1.xml

    r2f9131f r81fd230  
    88<?dbhtml filename="gcc-pass1.html"?>
    99
     10<indexterm zone="ch-tools-gcc-pass1">
     11<primary sortas="a-GCC">GCC</primary>
     12<secondary>tools, pass 1</secondary></indexterm>
     13
    1014<sect2 role="package"><title/>
     15<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
    1116
    1217<segmentedlist>
    … …  
    1621</segmentedlist>
    1722
     23<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/gcc.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
     24
    1825</sect2>
    1926
    … …  
    2128<title>Installation of GCC</title>
    2229
    23 <para>Create a build dir:</para>
     30<para>Unpack only the gcc-core tarball because neither the C++
     31compiler nor the test suite will be needed here.</para>
     32
     33<para>This package is known to have issues when its default
     34optimization flags (including the <parameter>-march</parameter> and
     35<parameter>-mcpu</parameter> options) are changed. If any environment
     36variables that override default optimizations have been defined, such
     37as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
     38unset them when building GCC.</para>
     39
     40<para>The GCC documentation recommends building GCC outside of the
     41source directory in a dedicated build directory:</para>
    2442
    2543<screen><userinput>mkdir ../gcc-build
    … …  
    2846<para>Prepare GCC for compilation:</para>
    2947
    30 <!--NEW-->
    31 <screen><userinput>CC="gcc -B/usr/bin" ../gcc-&gcc-version;/configure \
    32     --prefix=/tools --libexecdir=/tools/lib \
    33     --with-local-prefix=/tools --disable-nls \
    34     --enable-shared --enable-languages=c</userinput></screen>
     48<screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
     49    --libexecdir=/tools/lib --with-local-prefix=/tools \
     50    --disable-nls --enable-shared --enable-languages=c</userinput></screen>
     51
     52<para>The meaning of the configure options:</para>
     53
     54<variablelist>
     55<varlistentry>
     56<term><parameter>--with-local-prefix=/tools</parameter></term>
     57<listitem><para>The purpose of this switch is to remove <filename class="directory">/usr/local/include</filename>
     58from <command>gcc</command>'s include search path. This is not absolutely
     59essential, however, it helps to minimize the influence of the host
     60system.</para>
     61</listitem>
     62</varlistentry>
     63
     64<varlistentry>
     65<term><parameter>--enable-shared</parameter></term>
     66<listitem><para>This switch may seem counter-intuitive at first.
     67However, this switch allows the building of
     68<filename class="libraryfile">libgcc_s.so.1</filename> and
     69<filename class="libraryfile">libgcc_eh.a</filename>, and having
     70<filename class="libraryfile">libgcc_eh.a</filename> available ensures that the configure
     71script for Glibc (the next package we compile) produces the proper
     72results. Note that the GCC binaries will still be linked statically
     73because this is controlled by the <parameter>-static</parameter> value of
     74the <envar>BOOT_LDFLAGS</envar> variable in the next
     75step.</para></listitem>
     76</varlistentry>
     77
     78<varlistentry>
     79<term><parameter>--enable-languages=c</parameter></term>
     80<listitem><para>This option ensures that only the C compiler is built.
     81This option is only needed when you have downloaded and unpacked the
     82full GCC tarball, as opposed to just the gcc-core
     83tarball.</para></listitem>
     84</varlistentry>
     85</variablelist>
    3586
    3687<para>Continue with compiling the package:</para>
    … …  
    3889<screen><userinput>make BOOT_LDFLAGS="-static" bootstrap</userinput></screen>
    3990
    40 <para>Now install the package:</para>
     91<para>The meaning of the make parameters:</para>
     92
     93<variablelist>
     94<varlistentry>
     95<term><parameter>BOOT_LDFLAGS="-static"</parameter></term>
     96<listitem><para>This tells GCC to link its programs statically.</para></listitem>
     97</varlistentry>
     98
     99<varlistentry>
     100<term><parameter>bootstrap</parameter></term>
     101<listitem><para>This target does not just compile GCC, but compiles it
     102several times. It uses the programs compiled in a first round to
     103compile itself a second time, and then again a third time. It then
     104compares these second and third compiles to make sure it can reproduce
     105itself flawlessly.  This also implies that it was compiled
     106correctly.</para></listitem>
     107</varlistentry>
     108</variablelist>
     109
     110<para>Compilation is now complete. At this point, the test suite would
     111normally be run, but, as mentioned before, the test suite framework is
     112not in place yet. The benefits of running the tests at this point
     113are minimal since the programs from this first pass will soon be
     114replaced.</para>
     115
     116<para>Install the package:</para>
    41117
    42118<screen><userinput>make install</userinput></screen>
    43119
    44 <para>Create a symlink:</para>
     120<para>As a finishing touch, create a symlink. Many programs and
     121scripts run <command>cc</command> instead of <command>gcc</command>, which is used to keep programs generic
     122and therefore usable on all kinds of UNIX systems where the GNU C compiler
     123is not always installed. Running <command>cc</command> leaves the system administrator
     124free to decide which C compiler to install.</para>
    45125
    46126<screen><userinput>ln -s gcc /tools/bin/cc</userinput></screen>
    … …  
    48128</sect2>
    49129
     130<sect2 role="content"><title/>
     131<para>Details on this package are located in <xref
     132linkend="contents-gcc" role="."/></para>
     133</sect2>
     134
    50135</sect1>
     136
Note: See TracChangeset for help on using the changeset viewer.