diff options
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/aboutdebug.xml | 2 | ||||
| -rw-r--r-- | chapter06/bootscripts.xml | 2 | ||||
| -rw-r--r-- | chapter06/chapter06.xml | 6 | ||||
| -rw-r--r-- | chapter06/gcc-2953.xml | 2 | ||||
| -rw-r--r-- | chapter06/gcc.xml | 2 |
5 files changed, 7 insertions, 7 deletions
diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index ccf05b83e..6708deb54 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -41,7 +41,7 @@ or ELF binary), run <command>strip --strip-debug filename</command>. Wildcards can be used to treat multiple files (use something like <userinput>strip --strip-debug $LFS/tools/bin/*</userinput>).</para> -<para>For your convenience, <xref linkend="chapter09"/> includes one simple +<para>For your convenience, <xref linkend="chapter-finalizing"/> includes one simple command to strip all debugging symbols from all programs and libraries on your system. Additional information on optimization can be found in the hint at <ulink url="&hints-root;optimization.txt"/>.</para> diff --git a/chapter06/bootscripts.xml b/chapter06/bootscripts.xml index bb2a511ab..159470d1f 100644 --- a/chapter06/bootscripts.xml +++ b/chapter06/bootscripts.xml @@ -23,7 +23,7 @@ like something more radical, search the LFS mailing lists for depinit.</para> <para>If you decide to use BSD style, or some other style scripts, you can skip the next chapter when you arrive at it and move on to -<xref linkend="chapter08"/>.</para> +<xref linkend="chapter-mixture"/>.</para> <para>Install the boot scripts:</para> diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index ef78e75e7..44ec75c9e 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -1,4 +1,4 @@ -<chapter id="chapter06" xreflabel="Chapter 6"> +<chapter id="chapter-building-system" xreflabel="Chapter 6"> <title>Installing basic system software</title> <?dbhtml filename="chapter06.html" dir="chapter06"?> @@ -269,7 +269,7 @@ freely by the user, as well-written packages don't depend on GID numbers but use the group's name.</para> <para>To get rid of the "I have no name!" prompt, we will start a new shell. -Since we installed a full Glibc in <xref linkend="chapter05"/>, and have just +Since we installed a full Glibc in <xref linkend="chapter-temporary-tools"/>, and have just created the <filename>/etc/passwd</filename> and <filename>/etc/group</filename> files, user name and group name resolution will now work.</para> @@ -325,7 +325,7 @@ adjusted linker by running the following from within the <note><para>If you somehow missed the earlier warning to retain the Binutils source and build directories from the second pass in -<xref linkend="chapter05"/>, or otherwise accidentally deleted them or just +<xref linkend="chapter-temporary-tools"/>, or otherwise accidentally deleted them or just don't have access to them, don't worry, all is not lost. Just ignore the above command. The result will be that the next package, Binutils, will link against the Glibc libraries in <filename class="directory">/tools</filename> rather diff --git a/chapter06/gcc-2953.xml b/chapter06/gcc-2953.xml index e79db7dbf..171c4d908 100644 --- a/chapter06/gcc-2953.xml +++ b/chapter06/gcc-2953.xml @@ -28,7 +28,7 @@ default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building GCC.</para> <para>This is an older release of GCC which we are going to install for the -purpose of compiling the Linux kernel in <xref linkend="chapter08"/>. This +purpose of compiling the Linux kernel in <xref linkend="chapter-mixture"/>. This version is recommended by the kernel developers when you need absolute stability. Later versions of GCC have not received as much testing for Linux kernel compilation. Using a diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index 824307bd6..7cf0f81a4 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -92,7 +92,7 @@ compiler. To satisfy those packages, create a symlink:</para> we performed earlier in this chapter. Refer back to <xref linkend="ch-system-adjustingtoolchain"/> and repeat the check. If the results are wrong, then most likely you erroneously applied the GCC Specs patch from -<xref linkend="chapter05"/>.</para></note> +<xref linkend="chapter-temporary-tools"/>.</para></note> </sect2> |