Changeset ef93b66
- Timestamp:
- 09/27/2022 06:42:07 PM (18 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- dd7f9df
- Parents:
- ec7b0466
- Location:
- chapter04
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/aboutsbus.xml
rec7b0466 ref93b66 14 14 it takes to compile and install each package. Because Linux From 15 15 Scratch can be built on many different systems, it is impossible to 16 provide a ccurate time estimates. The biggest package (Glibc) will16 provide absolute time estimates. The biggest package (Glibc) will 17 17 take approximately 20 minutes on the fastest systems, but could take 18 18 up to three days on slower systems! Instead of providing actual times, … … 21 21 22 22 <para>The SBU measure works as follows. The first package to be compiled 23 from this bookis binutils in <xref linkend="chapter-cross-tools"/>. The24 time it takes to compile this package is what w ill be referredto as the25 Standard Build Unit or SBU. All other compile times will be expressed relative26 t o thistime.</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> 27 27 28 28 <para>For example, consider a package whose compilation time is 4.5 29 SBUs. This means that if asystem took 10 minutes to compile and29 SBUs. This means that if your system took 10 minutes to compile and 30 30 install the first pass of binutils, it will take 31 <emphasis>approximately</emphasis> 45 minutes to build th isexample 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> 33 33 34 <para> In general,SBUs are not entirely accurate because they depend on many34 <para>SBUs are not entirely accurate because they depend on many 35 35 factors, including the host system's version of GCC. They are provided here 36 36 to give an estimate of how long it might take to install a package, but the … … 46 46 <screen role="nodump"><userinput>export MAKEFLAGS='-j4'</userinput></screen> 47 47 48 <para>or justbuilding with:</para>48 <para>or by building with:</para> 49 49 50 50 <screen role="nodump"><userinput>make -j4</userinput></screen> … … 53 53 book will vary even more than they normally would. In some cases, the make 54 54 step will simply fail. Analyzing the output of the build process will also 55 be more difficult because the lines ofdifferent processes will be56 interleaved. If you run into a problem with a build step, revert backto a55 be more difficult because the lines from different processes will be 56 interleaved. If you run into a problem with a build step, revert to a 57 57 single processor build to properly analyze the error messages.</para> 58 58 </note> -
chapter04/abouttestsuites.xml
rec7b0466 ref93b66 28 28 <para>Running the test suites in <xref linkend="chapter-cross-tools"/> 29 29 and <xref linkend="chapter-temporary-tools"/> 30 is impossible, since theprograms are compiled with a cross-compiler,31 so are not supposed to be able torun on the build host.</para>30 is pointless; since the test programs are compiled with a cross-compiler, 31 they probably can't run on the build host.</para> 32 32 </note> 33 33 34 34 <para>A common issue with running the test suites for binutils and GCC 35 is running out of pseudo terminals (PTYs). This can result in a high35 is running out of pseudo terminals (PTYs). This can result in a large 36 36 number of failing tests. This may happen for several reasons, but the 37 37 most likely cause is that the host system does not have the … … 40 40 <ulink url="&lfs-root;lfs/faq.html#no-ptys"/>.</para> 41 41 42 <para>Sometimes package test suites will fail , butfor reasons which the42 <para>Sometimes package test suites will fail for reasons which the 43 43 developers are aware of and have deemed non-critical. Consult the logs located 44 44 at <ulink url="&test-results;"/> to verify whether or not these failures are 45 expected. This site is valid for all test s throughout this book.</para>45 expected. This site is valid for all test suites throughout this book.</para> 46 46 47 47 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.