Changeset ee714d3


Ignore:
Timestamp:
06/09/2020 09:26:11 PM (2 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, arm, ml-11.0, multilib, s6-init, trunk, xry111/clfs-ng, xry111/git-transition, xry111/glibc-2.34, xry111/lfs-next, xry111/tester-nohack, xry111/usr-move
Children:
79524a0
Parents:
b99b7d3
Message:

Text update to cross2 Chapter 4.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11913 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter04
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • chapter04/aboutsbus.xml

    rb99b7d3 ree714d3  
    2121
    2222  <para>The SBU measure works as follows. The first package to be compiled
    23   from this book is Binutils in <xref linkend="chapter-temporary-tools"/>. The
     23  from this book is binutils in <xref linkend="chapter-cross-tools"/>. The
    2424  time it takes to compile this package is what will be referred to as the
    2525  Standard Build Unit or SBU. All other compile times will be expressed relative
     
    2828  <para>For example, consider a package whose compilation time is 4.5
    2929  SBUs. This means that if a system took 10 minutes to compile and
    30   install the first pass of Binutils, it will take
     30  install the first pass of binutils, it will take
    3131  <emphasis>approximately</emphasis> 45 minutes to build this example package.
    32   Fortunately, most build times are shorter than the one for Binutils.</para>
     32  Fortunately, most build times are shorter than the one for binutils.</para>
    3333
    3434  <para>In general, SBUs are not entirely accurate because they depend on many
     
    4242    make" by either setting an environment variable or telling the
    4343    <command>make</command> program how many processors are available.  For
    44     instance, a Core2Duo can support two simultaneous processes with:</para>
     44    instance, an Intel i5-6500 COU  can support four simultaneous processes with:</para>
    4545
    46     <screen role="nodump"><userinput>export MAKEFLAGS='-j 2'</userinput></screen>
     46    <screen role="nodump"><userinput>export MAKEFLAGS='-j4'</userinput></screen>
    4747
    4848    <para>or just building with:</para>
    4949
    50     <screen role="nodump"><userinput>make -j2</userinput></screen>
     50    <screen role="nodump"><userinput>make -j4</userinput></screen>
    5151
    5252    <para>When multiple processors are used in this way, the SBU units in the
  • chapter04/abouttestsuites.xml

    rb99b7d3 ree714d3  
    1919
    2020  <para>Some test suites are more important than others. For example,
    21   the test suites for the core toolchain packages&mdash;GCC, Binutils, and
    22   Glibc&mdash;are of the utmost importance due to their central role in a
    23   properly functioning system. The test suites for GCC and Glibc can
     21  the test suites for the core toolchain packages&mdash;GCC, binutils, and
     22  glibc&mdash;are of the utmost importance due to their central role in a
     23  properly functioning system. The test suites for GCC and glibc can
    2424  take a very long time to complete, especially on slower hardware, but
    2525  are strongly recommended.</para>
    2626
    2727  <note>
    28     <para>Running the test suites in <xref linkend="chapter-temporary-tools"/>
     28    <para>Running the test suites in <xref linkend="chapter-cross-tools"/>
     29    and <xref linkend="chapter-temporary-tools"/>
    2930    is impossible, since the programs are compiled with a cross-compiler,
    3031    so are not supposed to be able to run on the build host.</para>
    3132  </note>
    3233
    33   <para>A common issue with running the test suites for Binutils and GCC
     34  <para>A common issue with running the test suites for binutils and GCC
    3435  is running out of pseudo terminals (PTYs). This can result in a high
    3536  number of failing tests. This may happen for several reasons, but the
  • chapter04/addinguser.xml

    rb99b7d3 ree714d3  
    1212
    1313  <para>When logged in as user <systemitem class="username">root</systemitem>,
    14   making a single mistake can damage or destroy a system. Therefore, we
    15   recommend building the packages in the next chapter as an unprivileged user.
     14  making a single mistake can damage or destroy a system. Therefore,
     15  the packages in the next two chapters are built as an unprivileged user.
    1616  You could use your own user name, but to make it easier to set up a clean
    1717  working environment, create a new user called <systemitem
     
    6363      <term><parameter>lfs</parameter></term>
    6464      <listitem>
    65         <para>This is the actual name for the created group and user.</para>
     65        <para>This is the actual name for the created user.</para>
    6666      </listitem>
    6767    </varlistentry>
     
    9696  <para>Next, login as user <systemitem class="username">lfs</systemitem>.
    9797  This can be done via a virtual console, through a display manager, or with
    98   the following substitute user command:</para>
     98  the following substitute/switch user command:</para>
    9999
    100100<screen role="nodump"><userinput>su - lfs</userinput></screen>
  • chapter04/settingenviron.xml

    rb99b7d3 ree714d3  
    5151
    5252  <variablelist>
    53     <title>The meaning of the command line options in <filename>.bashrc</filename></title>
     53    <title>The meaning of the settings in <filename>.bashrc</filename></title>
    5454
    5555    <varlistentry>
     
    137137  <para>By putting <filename class="directory">$LFS/tools/bin</filename> ahead of the
    138138  standard <envar>PATH</envar>, the cross-compiler installed at the beginning
    139   of <xref linkend="chapter-temporary-tools"/> is picked up by the shell
     139  of <xref linkend="chapter-cross-tools"/> is picked up by the shell
    140140  immediately after its installation. This, combined with turning off hashing,
    141141  limits the risk that the compiler from the host be used instead of the
     
    148148      <listitem>
    149149        <para>While the above commands have set some variables, in order
    150         to make them visible within any sub-shells, we export them</para>
     150        to make them visible within any sub-shells, we export them.</para>
    151151      </listitem>
    152152    </varlistentry>
Note: See TracChangeset for help on using the changeset viewer.