Ignore:
Timestamp:
11/04/2022 07:03:33 AM (18 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
multilib
Children:
381c8a7
Parents:
90fcd12 (diff), 5156c400 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Automatic merge of trunk into multilib

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter06/gcc-pass2.xml

    r90fcd12 r5f3a328  
    4949-->
    5050    <para>As in the first build of GCC, the GMP, MPFR, and MPC packages are
    51     required. Unpack the tarballs and move them into the required directory
    52     names:</para>
     51    required. Unpack the tarballs and move them into the required directories:</para>
    5352
    5453<screen><userinput remap="pre">tar -xf ../mpfr-&mpfr-version;.tar.xz
     
    145144          a cross-compiler is used for building GCC, and that compiler knows
    146145          that it has to look for headers and libraries in <filename
    147           class="directory">$LFS</filename>. But the build system of GCC uses
     146          class="directory">$LFS</filename>. But the build system for GCC uses
    148147          other tools, which are not aware of this location. This switch is
    149           needed to have them find the needed files in <filename
     148          needed so those tools will find the needed files in <filename
    150149          class="directory">$LFS</filename>, and not on the host.</para>
    151150        </listitem>
     
    155154        <term><parameter>--target=$LFS_TGT</parameter></term>
    156155        <listitem>
    157           <para>As we are cross-compiling GCC, it's impossible to build
     156          <para>We are cross-compiling GCC, so it's impossible to build
    158157          target libraries (<filename class="libraryfile">libgcc</filename>
    159158          and <filename class="libraryfile">libstdc++</filename>) with the
    160           compiled GCC binaries because these binaries won't run on the
    161           host distro.  GCC building system will attempt to use the
    162           C and C++ compilers on the host distro as a workaround by default.
    163           It's not supported to build GCC target libraries with a different
    164           version of GCC, so using host compilers may cause building
    165           failure.  This parameter ensures to build the libraries with GCC
    166           pass 1 and prevent the issue.</para>
     159          previously compiled GCC binaries&mdash;those binaries won't run on the
     160          host.  The GCC build system will attempt to use the host's
     161          C and C++ compilers as a workaround by default.
     162          Building the GCC target libraries with a different
     163          version of GCC is not supported, so using the host's compilers may cause
     164          the build to fail. This parameter ensures the libraries are built by GCC
     165          pass 1.</para>
    167166        </listitem>
    168167      </varlistentry>
     
    172171        <listitem>
    173172          <para>Allow <filename class="libraryfile">libstdc++</filename> to
    174           use shared <filename class="libraryfile">libgcc</filename> being
    175           built in this pass, instead of the static version built in GCC
    176           pass 1. This is needed for supporting C++ exception
     173          use the shared <filename class="libraryfile">libgcc</filename> being
     174          built in this pass, instead of the static version that was built in GCC
     175          pass 1. This is necessary to support C++ exception
    177176          handling.</para>
    178177        </listitem>
Note: See TracChangeset for help on using the changeset viewer.