- Timestamp:
- 06/09/2020 09:26:11 PM (4 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, 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:
- 79524a0
- Parents:
- b99b7d3
- Location:
- chapter04
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/aboutsbus.xml
rb99b7d3 ree714d3 21 21 22 22 <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"/>. The23 from this book is binutils in <xref linkend="chapter-cross-tools"/>. The 24 24 time it takes to compile this package is what will be referred to as the 25 25 Standard Build Unit or SBU. All other compile times will be expressed relative … … 28 28 <para>For example, consider a package whose compilation time is 4.5 29 29 SBUs. This means that if a system took 10 minutes to compile and 30 install the first pass of Binutils, it will take30 install the first pass of binutils, it will take 31 31 <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> 33 33 34 34 <para>In general, SBUs are not entirely accurate because they depend on many … … 42 42 make" by either setting an environment variable or telling the 43 43 <command>make</command> program how many processors are available. For 44 instance, a Core2Duo can support twosimultaneous processes with:</para>44 instance, an Intel i5-6500 COU can support four simultaneous processes with:</para> 45 45 46 <screen role="nodump"><userinput>export MAKEFLAGS='-j 2'</userinput></screen>46 <screen role="nodump"><userinput>export MAKEFLAGS='-j4'</userinput></screen> 47 47 48 48 <para>or just building with:</para> 49 49 50 <screen role="nodump"><userinput>make -j 2</userinput></screen>50 <screen role="nodump"><userinput>make -j4</userinput></screen> 51 51 52 52 <para>When multiple processors are used in this way, the SBU units in the -
chapter04/abouttestsuites.xml
rb99b7d3 ree714d3 19 19 20 20 <para>Some test suites are more important than others. For example, 21 the test suites for the core toolchain packages—GCC, Binutils, and22 Glibc—are of the utmost importance due to their central role in a23 properly functioning system. The test suites for GCC and Glibc can21 the test suites for the core toolchain packages—GCC, binutils, and 22 glibc—are of the utmost importance due to their central role in a 23 properly functioning system. The test suites for GCC and glibc can 24 24 take a very long time to complete, especially on slower hardware, but 25 25 are strongly recommended.</para> 26 26 27 27 <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"/> 29 30 is impossible, since the programs are compiled with a cross-compiler, 30 31 so are not supposed to be able to run on the build host.</para> 31 32 </note> 32 33 33 <para>A common issue with running the test suites for Binutils and GCC34 <para>A common issue with running the test suites for binutils and GCC 34 35 is running out of pseudo terminals (PTYs). This can result in a high 35 36 number of failing tests. This may happen for several reasons, but the -
chapter04/addinguser.xml
rb99b7d3 ree714d3 12 12 13 13 <para>When logged in as user <systemitem class="username">root</systemitem>, 14 making a single mistake can damage or destroy a system. Therefore, we15 recommend building the packages in the next chapteras 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. 16 16 You could use your own user name, but to make it easier to set up a clean 17 17 working environment, create a new user called <systemitem … … 63 63 <term><parameter>lfs</parameter></term> 64 64 <listitem> 65 <para>This is the actual name for the created group anduser.</para>65 <para>This is the actual name for the created user.</para> 66 66 </listitem> 67 67 </varlistentry> … … 96 96 <para>Next, login as user <systemitem class="username">lfs</systemitem>. 97 97 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> 99 99 100 100 <screen role="nodump"><userinput>su - lfs</userinput></screen> -
chapter04/settingenviron.xml
rb99b7d3 ree714d3 51 51 52 52 <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> 54 54 55 55 <varlistentry> … … 137 137 <para>By putting <filename class="directory">$LFS/tools/bin</filename> ahead of the 138 138 standard <envar>PATH</envar>, the cross-compiler installed at the beginning 139 of <xref linkend="chapter- temporary-tools"/> is picked up by the shell139 of <xref linkend="chapter-cross-tools"/> is picked up by the shell 140 140 immediately after its installation. This, combined with turning off hashing, 141 141 limits the risk that the compiler from the host be used instead of the … … 148 148 <listitem> 149 149 <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> 151 151 </listitem> 152 152 </varlistentry>
Note:
See TracChangeset
for help on using the changeset viewer.