Ignore:
Timestamp:
10/01/2022 08:03:20 AM (19 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/clfs-ng
Children:
ef1f48b
Parents:
259794e (diff), 2bf32ff (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:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter04/aboutsbus.xml

    r259794e rdd61c77  
    1414  it takes to compile and install each package. Because Linux From
    1515  Scratch can be built on many different systems, it is impossible to
    16   provide accurate time estimates. The biggest package (Glibc) will
     16  provide absolute time estimates. The biggest package (Glibc) will
    1717  take approximately 20 minutes on the fastest systems, but could take
    1818  up to three days on slower systems! Instead of providing actual times,
     
    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-cross-tools"/>. The
    24   time it takes to compile this package is what will be referred to as the
    25   Standard Build Unit or SBU. All other compile times will be expressed relative
    26   to this time.</para>
     23  is binutils in <xref linkend="chapter-cross-tools"/>. The
     24  time it takes to compile this package is what we will refer to as the
     25  Standard Build Unit or SBU. All other compile times will be expressed in
     26  terms of this unit of time.</para>
    2727
    2828  <para>For example, consider a package whose compilation time is 4.5
    29   SBUs. This means that if a system took 10 minutes to compile and
     29  SBUs. This means that if your system took 10 minutes to compile and
    3030  install the first pass of binutils, it will take
    31   <emphasis>approximately</emphasis> 45 minutes to build this example package.
    32   Fortunately, most build times are shorter than the one for binutils.</para>
     31  <emphasis>approximately</emphasis> 45 minutes to build the example package.
     32  Fortunately, most build times are shorter than one SBU.</para>
    3333
    34   <para>In general, SBUs are not entirely accurate because they depend on many
     34  <para>SBUs are not entirely accurate because they depend on many
    3535  factors, including the host system's version of GCC.  They are provided here
    3636  to give an estimate of how long it might take to install a package, but the
     
    5454    <screen role="nodump"><userinput>export MAKEFLAGS='-j4'</userinput></screen>
    5555
    56     <para>or just building with:</para>
     56    <para>or by building with:</para>
    5757
    5858    <screen role="nodump"><userinput>make -j4</userinput></screen>
     
    6161    book will vary even more than they normally would.  In some cases, the make
    6262    step will simply fail.  Analyzing the output of the build process will also
    63     be more difficult because the lines of different processes will be
    64     interleaved.  If you run into a problem with a build step, revert back to a
     63    be more difficult because the lines from different processes will be
     64    interleaved.  If you run into a problem with a build step, revert to a
    6565    single processor build to properly analyze the error messages.</para>
    6666  </note>
Note: See TracChangeset for help on using the changeset viewer.