Changeset 67c35bd
- Timestamp:
- 03/13/2005 10:56:18 PM (19 years ago)
- 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, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 0060429
- Parents:
- 6581f03
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r6581f03 r67c35bd 83 83 </listitem> 84 84 85 <listitem><para>March 13, 2005 [matt]: Reword About SBUs section to reflect the 86 earlier fix for bug 1061</para></listitem> 87 85 88 <listitem><para>March 13, 2005 [matt]: Dynamically link the pass1 toolchain to 86 89 workaround bug 1061 and remove all related explanatory text</para></listitem> -
chapter04/aboutsbus.xml
r6581f03 r67c35bd 14 14 take approximately 20 minutes on the fastest systems, but could take 15 15 up to three days on slower systems! Instead of providing actual times, 16 the Sta ticBuild Unit (SBU) measure will be16 the Standard Build Unit (SBU) measure will be 17 17 used instead.</para> 18 18 19 19 <para>The SBU measure works as follows. The first package to be compiled 20 from this book is the statically-linked Binutils in <xref 21 linkend="chapter-temporary-tools"/>. The time it takes to compile 22 this package is what will be referred to as the Static Build Unit 23 or SBU. All other compile times will be expressed relative to this 24 time.</para> 20 from this book is Binutils in <xref linkend="chapter-temporary-tools"/>. The 21 time it takes to compile this package is what will be referred to as the 22 Standard Build Unit or SBU. All other compile times will be expressed relative 23 to this time.</para> 25 24 26 25 <para>For example, consider a package whose compilation time is 4.5 27 26 SBUs. This means that if a system took 10 minutes to compile and 28 install the static Binutils, it will take 29 <emphasis>approximately</emphasis> 45 minutes to build this example 30 package. Fortunately, most build times are shorter than the one 31 for Binutils.</para> 27 install the first pass of Binutils, it will take 28 <emphasis>approximately</emphasis> 45 minutes to build this example package. 29 Fortunately, most build times are shorter than the one for Binutils.</para> 32 30 33 <para>Please note that if the system compiler on the host is GCC-2.x based, the 34 SBUs listed may be somewhat understated. This is because the SBU is 35 based on the very first package, compiled with the old GCC, while the 36 rest of the system is compiled with the newer GCC-&gcc-version; (which is 37 known to be approximately 30 percent slower). SBUs are also not 38 highly accurate for Symmetric Multi-Processor (SMP)-based machines.</para> 31 <para>In general, SBUs are not entirely accurate because they depend on many 32 factors, not just the GCC version. Note that on Symmetric Multi-Processor 33 (SMP)-based machines, SBUs are even less accurate. They are provided here to 34 give an estimate of how long it might take to install a package, but the numbers 35 can vary by as much as dozens of minutes in some cases.</para> 39 36 40 37 <para>To view actual timings for a number of specific machines, we recommend 41 38 <ulink url="&lfs-root;~bdubbs/"/>.</para> 42 39 43 <para>In general, SBUs are not very accurate because they depend on many44 factors, not just the GCC version. They are provided45 here to give an estimate of how long it might take to46 install a package, but the numbers can vary by as much as dozens of47 minutes in some cases.</para>48 49 40 </sect1> 50 41
Note:
See TracChangeset
for help on using the changeset viewer.