Changeset f6820bb6


Ignore:
Timestamp:
10/30/2022 02:23:55 PM (18 months ago)
Author:
David Bryant <davidbryant@…>
Branches:
11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/update-glibc
Children:
6b052ef
Parents:
019499e
Message:

Corrected spelling here and there. Regularized capitaization of package
names, corrected idiom / punctuation, and removed extraneous verbiage.

Location:
chapter05
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter05/binutils-pass1.xml

    r019499e rf6820bb6  
    8585        <listitem>
    8686          <para>This tells the configure script to prepare to install the
    87           binutils programs in the <filename
     87          Binutils programs in the <filename
    8888          class="directory">$LFS/tools</filename> directory.</para>
    8989        </listitem>

  • chapter05/gcc-pass1.xml

    r019499e rf6820bb6  
    5151
    5252    <note><para>There are frequent misunderstandings about this chapter.  The
    53     procedures are the same as every other chapter as explained earlier (<xref
    54     linkend='buildinstr'/>).  First extract the gcc tarball from the sources
    55     directory and then change to the directory created.  Only then should you
     53    procedures are the same as every other chapter, as explained earlier (<xref
     54    linkend='buildinstr'/>).  First, extract the gcc-&gcc-version; tarball from the sources
     55    directory, and then change to the directory created.  Only then should you
    5656    proceed with the instructions below.</para></note>
    5757
    … …  
    108108        <term><parameter>--with-glibc-version=&glibc-version;</parameter></term>
    109109        <listitem>
    110           <para>This option specifies the version of glibc which will be
     110          <para>This option specifies the version of Glibc which will be
    111111          used on the target. It is not relevant to the libc of the host
    112           distro because everything compiled by pass1 gcc will run in the
     112          distro because everything compiled by pass1 GCC will run in the
    113113          chroot environment, which is isolated from libc of the host
    114114          distro.</para>
    … …  
    153153        <listitem>
    154154          <para>This switch forces GCC to link its internal libraries
    155           statically. We need this because the shared libraries require glibc,
     155          statically. We need this because the shared libraries require Glibc,
    156156          which is not yet installed on the target system.</para>
    157157        </listitem>
    … …  
    205205    does not exist, so the internal header that has just been installed is a
    206206    partial, self-contained file and does not include the extended features of
    207     the system header. This is adequate for building glibc, but the full
     207    the system header. This is adequate for building Glibc, but the full
    208208    internal header will be needed later.  Create a full version of the internal
    209209    header using a command that is identical to what the GCC build system does

  • chapter05/glibc.xml

    r019499e rf6820bb6  
    5959      <para>
    6060        The above command is correct.  The <command>ln</command> command has
    61         a few syntactic versions, so be sure to check
     61        several syntactic versions, so be sure to check
    6262        <command>info coreutils ln</command> and <filename>ln(1)</filename>
    63         before reporting what you may think is an error.
     63        before reporting what may appear to be an error.
    6464      </para>
    6565    </note>
    6666
    67     <para>Some of the Glibc programs use the non-FHS compliant
     67    <para>Some of the Glibc programs use the non-FHS-compliant
    6868    <filename class="directory">/var/db</filename> directory to store their
    6969    runtime data. Apply the following patch to make such programs store their
    … …  
    129129        <listitem>
    130130          <para>This ensures that the library is installed in /usr/lib instead
    131           of the default /lib64 on 64 bit machines.</para>
     131          of the default /lib64 on 64-bit machines.</para>
    132132        </listitem>
    133133      </varlistentry>
    … …  
    147147    <para>The missing or incompatible <command>msgfmt</command> program is
    148148    generally harmless. This <command>msgfmt</command> program is part of the
    149     Gettext package which the host distribution should provide.</para>
     149    Gettext package, which the host distribution should provide.</para>
    150150
    151151    <note><para>There have been reports that this package may fail when
    152     building as a "parallel make".  If this occurs, rerun the make command
    153     with a "-j1" option.</para></note>
     152    building as a "parallel make".  If that occurs, rerun the make command
     153    with the "-j1" option.</para></note>
    154154
    155155    <para>Compile the package:</para>
    … …  
    162162    recommendations, you are building as
    163163    <systemitem class="username">root</systemitem>, the next command will
    164     install the newly built glibc to your host system, which most likely
    165     will render it unusable. So double check that the environment is
    166     correctly set, before running the following command.</para></warning>
     164    install the newly built Glibc to your host system, which will almost
     165    certainly render it unusable. So double-check that the environment is
     166    correctly set, and that you are not &root;, before running the following command.</para></warning>
    167167
    168168<screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
    … …  
    178178          installed. If it is not set, it defaults to the root (<filename
    179179          class="directory">/</filename>) directory. Here we specify that
    180           the package be installed in <filename class="directory">$LFS
    181           </filename>, which will become the root after <xref linkend=
     180          the package is installed in <filename class="directory">$LFS
     181          </filename>, which will become the root directory in <xref linkend=
    182182          "ch-tools-chroot"/>.</para>
    183183        </listitem>
    … …  
    186186    </variablelist>
    187187
    188     <para>Fix hardcoded path to the executable loader in
     188    <para>Fix a hard coded path to the executable loader in the
    189189    <command>ldd</command> script:</para>
    190190
    … …  
    207207      <filename>/lib/ld-linux.so.2</filename>.</para>
    208208
    209       <para>If the output is not shown as above or there was no output at all,
     209      <para>If the output is not as shown above, or there is no output at all,
    210210      then something is wrong. Investigate and retrace the steps to find out
    211211      where the problem is and correct it. This issue must be resolved before
    212       continuing on.</para>
     212      continuing.</para>
    213213
    214214      <para>Once all is well, clean up the test file:</para>
    … …  
    218218    </caution>
    219219
    220     <note><para>Building packages in the next chapter will serve as an
     220    <note><para>Building the packages in the next chapter will serve as an
    221221    additional check that the toolchain has been built properly. If some
    222     package, especially binutils-pass2 or gcc-pass2, fails to build, it is
     222    package, especially Binutils-pass2 or GCC-pass2, fails to build, it is
    223223    an indication that something has gone wrong with the
    224     previous Binutils, GCC, or Glibc installations.</para></note>
     224    preceding Binutils, GCC, or Glibc installations.</para></note>
    225225
    226226    <para>Now that our cross-toolchain is complete, finalize the installation
    227     of the limits.h header. For doing so, run a utility provided by the GCC
     227    of the limits.h header. To do this, run a utility provided by the GCC
    228228    developers:</para>
    229229

  • chapter05/libstdc++.xml

    r019499e rf6820bb6  
    2929    (part of GCC is written in C++), but we had to defer its installation
    3030    when we built <xref linkend="ch-tools-gcc-pass1"/>
    31     because it depends on glibc, which was not yet available in the target
     31    because Libstdc++ depends on Glibc, which was not yet available in the target
    3232    directory.
    3333    </para>
    … …  
    5454    </note>
    5555
    56     <para>Create a separate build directory for libstdc++ and enter it:</para>
     56    <para>Create a separate build directory for Libstdc++ and enter it:</para>
    5757
    5858<screen><userinput remap="pre">mkdir -v build
    5959cd       build</userinput></screen>
    6060
    61     <para>Prepare libstdc++ for compilation:</para>
     61    <para>Prepare Libstdc++ for compilation:</para>
    6262
    6363<screen><userinput remap="configure">../libstdc++-v3/configure           \
    … …  
    7676        <term><parameter>--host=...</parameter></term>
    7777        <listitem>
    78           <para>Specifies that the cross compiler we have just built
     78          <para>Specifies that the cross-compiler we have just built
    7979          should be used instead of the one in
    8080          <filename>/usr/bin</filename>.</para>
    … …  
    9494        <listitem>
    9595          <para>This specifies the installation directory for include files.
    96           Because libstdc++ is the standard C++ library for LFS, this
     96          Because Libstdc++ is the standard C++ library for LFS, this
    9797          directory should match the location where the C++ compiler
    9898          (<command>$LFS_TGT-g++</command>) would search for the
    9999          standard C++ include files. In a normal build, this information
    100           is automatically passed to the libstdc++ <command>configure</command>
     100          is automatically passed to the Libstdc++ <command>configure</command>
    101101          options from the top level directory. In our case, this information
    102102          must be explicitly given.
    103103          The C++ compiler will prepend the sysroot path
    104           <filename class="directory">$LFS</filename> (specified building
    105           GCC pass 1) to the include file search path, so it will actually
     104          <filename class="directory">$LFS</filename> (specified when building
     105          GCC-pass1) to the include file search path, so it will actually
    106106          search in
    107107          <filename class="directory">$LFS/tools/$LFS_TGT/include/c++/&gcc-version;</filename>.
    108108          The combination of the <parameter>DESTDIR</parameter>
    109109          variable (in the <command>make install</command> command below)
    110           and this switch ensures to install the headers there.</para>
     110          and this switch causes the headers to be installed there.</para>
    111111        </listitem>
    112112      </varlistentry>
    … …  
    114114    </variablelist>
    115115
    116     <para>Compile libstdc++ by running:</para>
     116    <para>Compile Libstdc++ by running:</para>
    117117
    118118<screen><userinput remap="make">make</userinput></screen>
    … …  
    123123
    124124    <para>Remove the libtool archive files because they are harmful for
    125     cross compilation:</para>
     125    cross-compilation:</para>
    126126
    127127<screen><userinput remap="install">rm -v $LFS/usr/lib/lib{stdc++,stdc++fs,supc++}.la</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.