diff options
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/chapter05.xml | 12 | ||||
| -rw-r--r-- | chapter05/gcc-pass2.xml | 2 | ||||
| -rw-r--r-- | chapter05/glibc.xml | 6 | ||||
| -rw-r--r-- | chapter05/tcl.xml | 2 |
4 files changed, 11 insertions, 11 deletions
diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index a2734acc8..8e5699990 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -1,4 +1,4 @@ -<chapter id="chapter05" xreflabel="Chapter 5"> +<chapter id="chapter-temporary-tools" xreflabel="Chapter 5"> <title>Constructing a temporary system</title> <?dbhtml filename="chapter05.html" dir="chapter05"?> @@ -71,10 +71,10 @@ details behind the overall build method. It's not essential that you understand everything here immediately. Most of it will make sense once you have performed an actual build. Feel free to refer back here at any time.</para> -<para>The overall goal of <xref linkend="chapter05"/> is to provide a sane, +<para>The overall goal of <xref linkend="chapter-temporary-tools"/> is to provide a sane, temporary environment that we can chroot into, and from which we can produce a clean, trouble-free build of the target LFS system in -<xref linkend="chapter06"/>. Along the way, we attempt to divorce ourselves +<xref linkend="chapter-building-system"/>. Along the way, we attempt to divorce ourselves from the host system as much as possible, and in so doing build a self-contained and self-hosted toolchain. It should be noted that the build process has been designed in such a way so as to minimize the risks for @@ -109,7 +109,7 @@ the <filename>shlib-versions</filename> file in the root of the Glibc source tree.</para> </important> -<para>Some key technical points of how the <xref linkend="chapter05"/> build +<para>Some key technical points of how the <xref linkend="chapter-temporary-tools"/> build method works:</para> <itemizedlist> @@ -207,10 +207,10 @@ would defeat our goal of getting away from the host.</para> <emphasis>--with-lib-path</emphasis> configure switch to control <command>ld</command>'s library search path. From this point onwards, the core toolchain is self-contained and self-hosted. The remainder of the -<xref linkend="chapter05"/> packages all build against the new Glibc in +<xref linkend="chapter-temporary-tools"/> packages all build against the new Glibc in <filename class="directory">/tools</filename> and all is well.</para> -<para>Upon entering the chroot environment in <xref linkend="chapter06"/>, the +<para>Upon entering the chroot environment in <xref linkend="chapter-building-system"/>, the first major package we install is Glibc, due to its self-sufficient nature that we mentioned above. Once this Glibc is installed into <filename class="directory">/usr</filename>, we perform a quick changeover of diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 462f92f0b..b8dcbaa60 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -50,7 +50,7 @@ process is warranted here. Under normal circumstances, the GCC fixincludes script scans your system for header files that need to be fixed. It might find that some Glibc header files on your host system need to be fixed, fix them and put them in the GCC private include directory. Then, later on in -<xref linkend="chapter06"/>, after we've installed the newer Glibc, this +<xref linkend="chapter-building-system"/>, after we've installed the newer Glibc, this private include directory would be searched before the system include directory, resulting in GCC finding the fixed headers from the host system, which would most likely not match the Glibc version actually used for the LFS diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 5b5f1d77e..1340cc9c0 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -90,7 +90,7 @@ so:</para> system, in particular the kernel. Additionally, here in this chapter some tests can be adversely affected by existing tools or environmental issues on the host system. Of course, these won't be a problem when we run the Glibc test suite -inside the chroot environment of <xref linkend="chapter06"/>. In general, the +inside the chroot environment of <xref linkend="chapter-building-system"/>. In general, the Glibc test suite is always expected to pass. However, as mentioned above, some failures are unavoidable in certain circumstances. Here is a list of the most common issues we are aware of:</para> @@ -117,9 +117,9 @@ fail due to test timeouts being exceeded.</para></listitem> </itemizedlist> <para>In summary, don't worry too much if you see Glibc test suite failures -here in this chapter. The Glibc in <xref linkend="chapter06"/> is the one we'll +here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is the one we'll ultimately end up using so that is the one we would really like to see pass. -But please keep in mind, even in <xref linkend="chapter06"/> some failures +But please keep in mind, even in <xref linkend="chapter-building-system"/> some failures could still occur -- the <emphasis>math</emphasis> tests for example. When experiencing a failure, make a note of it, then continue by reissuing the <command>make check</command>. The test suite diff --git a/chapter05/tcl.xml b/chapter05/tcl.xml index 4788f3875..1668a895d 100644 --- a/chapter05/tcl.xml +++ b/chapter05/tcl.xml @@ -48,7 +48,7 @@ here are not surprising, but are not considered critical:</para> Coordinated Universal Time (UTC) also known as Greenwich Mean Time (GMT), but only for the duration of the test suite run. This ensures the clock tests are exercised correctly. More information on the TZ environment variable will be -given later on in <xref linkend="chapter07"/>.</para></listitem> +given later on in <xref linkend="chapter-bootscripts"/>.</para></listitem> </itemizedlist> <para>Sometimes package test suites will give false failures. You can |