Changeset 0678bd4 for chapter04


Ignore:
Timestamp:
03/02/2023 03:16:03 AM (16 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/clfs-ng
Children:
5c3ffcb9
Parents:
985d253 (diff), 55a4043 (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

    r985d253 r0678bd4  
    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 absolute time estimates. The biggest package (Glibc) will
    17   take approximately 20 minutes on the fastest systems, but could take
    18   up to three days on slower systems! Instead of providing actual times,
     16  provide absolute time estimates. The biggest package (gcc) will
     17  take approximately 5 minutes on the fastest systems, but could take
     18  days on slower systems! Instead of providing actual times,
    1919  the Standard Build Unit (SBU) measure will be
    2020  used instead.</para>
    2121
    22   <para>The SBU measure works as follows. The first package to be compiled
    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>
     22  <para>The SBU measure works as follows. The first package to be compiled is
     23  binutils in <xref linkend="chapter-cross-tools"/>. The time it takes to
     24  compile using one core is what we will refer to as the Standard
     25  Build Unit or SBU. All other compile times will be expressed in terms of this
     26  unit of time.</para>
    2727
    2828  <para>For example, consider a package whose compilation time is 4.5
     
    6464    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>
     66
     67    <para>The times presented here are based upon using four cores (-j4). The
     68    times in Chapter 8 also include the time to run the regression tests for
     69    the package unless specified otherwise.</para>
     70
    6671  </note>
    6772
Note: See TracChangeset for help on using the changeset viewer.