Changeset cc0e77d


Ignore:
Timestamp:
09/29/2022 09:30:17 PM (2 months ago)
Author:
David Bryant <davidbryant@…>
Branches:
multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/pip3, xry111/rust-wip-20221008
Children:
7978900, e18ba69
Parents:
eb30b32
Message:

Fix English idiom / clarify "General Instructions" section.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • part3intro/generalinstructions.xml

    reb30b32 rcc0e77d  
    1212  <title>General Compilation Instructions</title>
    1313
    14   <para>When building packages there are several assumptions made within
    15   the instructions:</para>
     14  <para>Here are some things you should know about building each package:</para>
    1615
    1716  <itemizedlist>
    1817
    1918  <listitem>
    20     <para>Several of the packages are patched before compilation, but only when
     19    <para>Several packages are patched before compilation, but only when
    2120    the patch is needed to circumvent a problem. A patch is often needed in
    22     both this and the following chapters, but sometimes in only one location.
     21    both the current and the following chapters, but sometimes, when the same package
     22    is built more than once, the patch is not needed right away.
    2323    Therefore, do not be concerned if instructions for a downloaded patch seem
    2424    to be missing.  Warning messages about <emphasis>offset</emphasis> or
    2525    <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do
    26     not worry about these warnings, as the patch was still successfully
     26    not worry about these warnings; the patch was still successfully
    2727    applied.</para>
    2828  </listitem>
    2929
    3030  <listitem>
    31     <para>During the compilation of most packages, there will be several
    32     warnings that scroll by on the screen. These are normal and can safely be
    33     ignored.  These warnings are as they appear&mdash;warnings about
     31    <para>During the compilation of most packages, some
     32    warnings will scroll by on the screen. These are normal and can safely be
     33    ignored.  These warnings are usually about
    3434    deprecated, but not invalid, use of the C or C++ syntax. C standards change
    35     fairly often, and some packages still use the older standard. This is not a
    36     problem, but does prompt the warning.</para>
     35    fairly often, and some packages have not yet been updated. This is not a
     36    serious problem, but it does cause the warnings to appear.</para>
    3737  </listitem>
    3838
     
    7070
    7171        <listitem override='bullet'><para><command>/usr/bin/yacc</command> is a
    72         symbolic link to <command>bison</command> or a small script that
     72        symbolic link to <command>bison</command>, or to a small script that
    7373        executes bison.</para></listitem>
    7474
     
    7777
    7878    <important>
    79       <para>To re-emphasize the build process:</para>
     79      <para>Here is a synopsis of the build process.</para>
    8080
    8181      <orderedlist numeration="arabic" spacing="compact">
    8282        <listitem>
    8383          <para>Place all the sources and patches in a directory that will be
    84           accessible from the chroot environment such as
     84          accessible from the chroot environment, such as
    8585          <filename class="directory">/mnt/lfs/sources/</filename>.<!-- Do
    8686          <emphasis>not</emphasis> put sources in
     
    8888        </listitem>
    8989        <listitem>
    90           <para>Change to the sources directory.</para>
     90          <para>Change to the <filename class="directory">/mnt/lfs/sources/</filename> directory.</para>
    9191        </listitem>
    9292        <listitem id='buildinstr' xreflabel='Package build instructions'>
     
    9898              <xref linkend="chapter-temporary-tools"/>, ensure you are
    9999              the <emphasis>lfs</emphasis> user when extracting the package.</para>
    100               <para>All methods to get the source code tree being built
    101               in-position, except extracting the package tarball, are not
    102               supported. Notably, using <command>cp -R</command> to copy the
     100            <para>Do not use any method except the <command>tar</command> command
     101              to extract the source code. Notably, using the <command>cp -R</command>
     102              command to copy the
    103103              source code tree somewhere else can destroy links and
    104               timestamps in the sources tree and cause building
    105               failure.</para>
     104              timestamps in the source tree, and cause the build to fail.</para>
    106105            </listitem>
    107106            <listitem>
     
    110109            </listitem>
    111110            <listitem>
    112               <para>Follow the book's instructions for building the package.</para>
     111              <para>Follow the instructions for building the package.</para>
    113112            </listitem>
    114113            <listitem>
    115               <para>Change back to the sources directory.</para>
     114              <para>Change back to the sources directory when the build is complete.</para>
    116115            </listitem>
    117116            <listitem>
Note: See TracChangeset for help on using the changeset viewer.