- Timestamp:
- 02/04/2004 10:23:18 PM (20 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.0, 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, v5_1, v5_1_1, 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:
- 91e8861
- Parents:
- fe5b13b
- Location:
- chapter02
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/aboutlfs.xml
rfe5b13b rdcff046 7 7 the directory where the partition that contains the LFS system is mounted. How 8 8 to create and where to mount the partition will be explained in full detail in 9 <xref linkend="chapter 03"/>. For the moment let's assume that the LFS partition9 <xref linkend="chapter-making-space"/>. For the moment let's assume that the LFS partition 10 10 is mounted on <filename>/mnt/lfs</filename>.</para> 11 11 -
chapter02/aboutsbus.xml
rfe5b13b rdcff046 13 13 14 14 <para>It works like this: the first package you compile in this book is the 15 statically linked Binutils in <xref linkend="chapter 05"/>, and the time it15 statically linked Binutils in <xref linkend="chapter-temporary-tools"/>, and the time it 16 16 takes to compile this package is what we call the "Static Binutils Unit" or 17 17 "SBU". All other compile times will be expressed relative to this time.</para> -
chapter02/abouttestsuites.xml
rfe5b13b rdcff046 17 17 18 18 <para>Experience has shown us that there is little to be gained from running 19 the test suites in <xref linkend="chapter 05"/>. There can be no escaping the19 the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no escaping the 20 20 fact that the host system always exerts influence on the tests in that chapter, 21 21 often causing weird and inexplicable failures. Not only that, the tools built 22 in <xref linkend="chapter 05"/> are temporary and eventually discarded. For the22 in <xref linkend="chapter-temporary-tools"/> are temporary and eventually discarded. For the 23 23 average reader of this book we recommend <emphasis>not</emphasis> to run the 24 test suites in <xref linkend="chapter 05"/>. The instructions for running those24 test suites in <xref linkend="chapter-temporary-tools"/>. The instructions for running those 25 25 test suites are still provided for the benefit of testers and developers, but 26 26 they are strictly optional for everyone else.</para> … … 36 36 reasons. Most likely is that the host system doesn't have the 37 37 <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in 38 more detail later on in <xref linkend="chapter 05"/>.</para></note>38 more detail later on in <xref linkend="chapter-temporary-tools"/>.</para></note> 39 39 40 40 </sect1> -
chapter02/chapter02.xml
rfe5b13b rdcff046 1 <chapter id="chapter 02" xreflabel="Chapter 2">1 <chapter id="chapter-preparation" xreflabel="Chapter 2"> 2 2 <title>Important information</title> 3 3 <?dbhtml filename="chapter02.html" dir="chapter02"?>
Note:
See TracChangeset
for help on using the changeset viewer.