r4131 - branches/testing/BOOK/chapter05

manuel at linuxfromscratch.org manuel at linuxfromscratch.org
Sun Sep 5 04:18:44 PDT 2004


Author: manuel
Date: 2004-09-05 05:18:43 -0600 (Sun, 05 Sep 2004)
New Revision: 4131

Modified:
   branches/testing/BOOK/chapter05/adjusting.xml
   branches/testing/BOOK/chapter05/binutils-pass1.xml
   branches/testing/BOOK/chapter05/binutils-pass2.xml
   branches/testing/BOOK/chapter05/coreutils.xml
   branches/testing/BOOK/chapter05/dejagnu.xml
   branches/testing/BOOK/chapter05/expect.xml
   branches/testing/BOOK/chapter05/flex.xml
   branches/testing/BOOK/chapter05/gcc-pass1.xml
   branches/testing/BOOK/chapter05/gcc-pass2.xml
   branches/testing/BOOK/chapter05/gettext.xml
   branches/testing/BOOK/chapter05/glibc.xml
   branches/testing/BOOK/chapter05/introduction.xml
   branches/testing/BOOK/chapter05/kernel-headers.xml
   branches/testing/BOOK/chapter05/m4.xml
   branches/testing/BOOK/chapter05/tcl.xml
   branches/testing/BOOK/chapter05/toolchaintechnotes.xml
Log:
Tags corrections, Chapter 5.

Modified: branches/testing/BOOK/chapter05/adjusting.xml
===================================================================
--- branches/testing/BOOK/chapter05/adjusting.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/adjusting.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -53,8 +53,8 @@
 
 <important><para>If working on a platform where the name of the
 dynamic linker is something other than
-<filename>ld-linux.so.2</filename>, replace
-<filename>ld-linux.so.2</filename> with the name of the platform's
+<filename class="libraryfile">ld-linux.so.2</filename>, replace
+<quote>ld-linux.so.2</quote> with the name of the platform's
 dynamic linker in the above commands. Refer back to <xref
 linkend="ch-tools-toolchaintechnotes" role=","/> if
 necessary.</para></important>
@@ -91,12 +91,12 @@
 find out where the problem is and correct it. This issue must be
 resolved before continuing on. First, perform the sanity check again,
 using <command>gcc</command> instead of <command>cc</command>. If this
-works, then the <filename>/tools/bin/cc</filename> symlink is missing.
+works, then the <filename class="symlink">/tools/bin/cc</filename> symlink is missing.
 Revisit <xref linkend="ch-tools-gcc-pass1" role=","/> and install the symlink.
-Next, ensure that the PATH is correct. This can be checked by running
+Next, ensure that the <envar>PATH</envar> is correct. This can be checked by running
 <command>echo $PATH</command> and verifying that <filename
 class="directory">/tools/bin</filename> is at the head of the list. If
-the PATH is wrong it could mean that you are not logged in as user
+the <envar>PATH</envar> is wrong it could mean that you are not logged in as user
 <emphasis>lfs</emphasis> or that something went wrong back in <xref
 linkend="ch-tools-settingenviron" role="."/> Another option is that something
 may have gone wrong with the specs file amendment above. In this case,

Modified: branches/testing/BOOK/chapter05/binutils-pass1.xml
===================================================================
--- branches/testing/BOOK/chapter05/binutils-pass1.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/binutils-pass1.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -36,7 +36,7 @@
 optimization flags (including the <parameter>-march</parameter> and
 <parameter>-mcpu</parameter> options) are changed. If any environment
 variables that override default optimizations have been defined, such
-as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
+as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building Binutils.</para>
 
 <para>The Binutils documentation recommends building Binutils outside of the
@@ -129,8 +129,9 @@
 <term><parameter>-C ld LDFLAGS="-all-static"
 LIB_PATH=/tools/lib</parameter></term>
 <listitem><para>This option rebuilds everything in the
-<filename class="directory">ld</filename> subdirectory. Specifying the LIB_PATH
-Makefile variable on the command line allows us to override the default value
+<filename class="directory">ld</filename> subdirectory. Specifying 
+the <envar>LIB_PATH</envar> Makefile variable on the command 
+line allows us to override the default value
 and point it to the temporary tools location. The value of this variable
 specifies the linker's default library search path. This preparation
 is used later in the chapter.</para></listitem>

Modified: branches/testing/BOOK/chapter05/binutils-pass2.xml
===================================================================
--- branches/testing/BOOK/chapter05/binutils-pass2.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/binutils-pass2.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -35,7 +35,7 @@
 optimization flags (including the <parameter>-march</parameter> and
 <parameter>-mcpu</parameter> options) are changed. If any environment
 variables that override default optimizations have been defined, such
-as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
+as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building Binutils.</para>
 
 <para>Create a separate build directory again:</para>

Modified: branches/testing/BOOK/chapter05/coreutils.xml
===================================================================
--- branches/testing/BOOK/chapter05/coreutils.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/coreutils.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -39,10 +39,10 @@
 syntax is so pervasive that compatibility should be preserved until
 the many places where it is used can be updated. Backwards
 compatibility is achieved by setting the
-<emphasis>DEFAULT_POSIX2_VERSION</emphasis> environment variable to
+<envar>DEFAULT_POSIX2_VERSION</envar> environment variable to
 <quote>199209</quote> in the above command. If you do not want
 Coreutils to be backwards compatible with the traditional syntax, then
-omit setting the <emphasis>DEFAULT_POSIX2_VERSION</emphasis>
+omit setting the <envar>DEFAULT_POSIX2_VERSION</envar>
 environment variable. It is important to remember that doing so will
 have consequences, including the need to patch the many packages that
 still use the old syntax. Therefore, it is recommended that the

Modified: branches/testing/BOOK/chapter05/dejagnu.xml
===================================================================
--- branches/testing/BOOK/chapter05/dejagnu.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/dejagnu.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-dejagnu" xreflabel="DejaGNU" role="wrap">
+<sect1 id="ch-tools-dejagnu" role="wrap">
 <title>DejaGNU-&dejagnu-version;</title>
 <?dbhtml filename="dejagnu.html"?>
 

Modified: branches/testing/BOOK/chapter05/expect.xml
===================================================================
--- branches/testing/BOOK/chapter05/expect.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/expect.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-expect" xreflabel="Expect" role="wrap">
+<sect1 id="ch-tools-expect" role="wrap">
 <title>Expect-&expect-version;</title>
 <?dbhtml filename="expect.html"?>
 

Modified: branches/testing/BOOK/chapter05/flex.xml
===================================================================
--- branches/testing/BOOK/chapter05/flex.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/flex.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-flex" xreflabel="Flex" role="wrap">
+<sect1 id="ch-tools-flex" role="wrap">
 <title>Flex-&flex-version;</title>
 <?dbhtml filename="flex.html"?>
 

Modified: branches/testing/BOOK/chapter05/gcc-pass1.xml
===================================================================
--- branches/testing/BOOK/chapter05/gcc-pass1.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/gcc-pass1.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -34,7 +34,7 @@
 optimization flags (including the <parameter>-march</parameter> and
 <parameter>-mcpu</parameter> options) are changed. If any environment
 variables that override default optimizations have been defined, such
-as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
+as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building GCC.</para>
 
 <para>The GCC documentation recommends building GCC outside of the
@@ -64,13 +64,13 @@
 <term><parameter>--enable-shared</parameter></term>
 <listitem><para>This switch may seem counter-intuitive at first.
 However, this switch allows the building of
-<filename>libgcc_s.so.1</filename> and
-<filename>libgcc_eh.a</filename>, and having
-<filename>libgcc_eh.a</filename> available ensures that the configure
+<filename class="libraryfile">libgcc_s.so.1</filename> and
+<filename class="libraryfile">libgcc_eh.a</filename>, and having
+<filename class="libraryfile">libgcc_eh.a</filename> available ensures that the configure
 script for Glibc (the next package we compile) produces the proper
 results. Note that the GCC binaries will still be linked statically
 because this is controlled by the <parameter>-static</parameter> value of
-the <emphasis>BOOT_LDFLAGS</emphasis> variable in the next
+the <envar>BOOT_LDFLAGS</envar> variable in the next
 step.</para></listitem>
 </varlistentry>
 

Modified: branches/testing/BOOK/chapter05/gcc-pass2.xml
===================================================================
--- branches/testing/BOOK/chapter05/gcc-pass2.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/gcc-pass2.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -30,7 +30,7 @@
 optimization flags (including the <parameter>-march</parameter> and
 <parameter>-mcpu</parameter> options) are changed. If any environment
 variables that override default optimizations have been defined, such
-as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
+as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building GCC.</para>
 
 <para>The tools required to test GCC and Binutils—Tcl, Expect
@@ -81,7 +81,7 @@
 Glibc version used for the LFS system.</para>
 
 <para>The second patch changes GCC's default location of the dynamic
-linker (typically <filename>ld-linux.so.2</filename>). It also removes
+linker (typically <filename class="libraryfile">ld-linux.so.2</filename>). It also removes
 <filename class="directory">/usr/include</filename> from GCC's include
 search path. Patching now rather than adjusting the specs file after
 installation ensures that the new dynamic linker is used during the
@@ -150,8 +150,8 @@
 <varlistentry>
 <term><parameter>--disable-libstdcxx-pch</parameter></term>
 <listitem><para>Do not build the pre-compiled header (PCH) for
-libstdc++. It takes up a lot of space, and we have no use for
-it.</para></listitem>
+<filename class="libraryfile">libstdc++</filename>. It takes up a lot of space,
+and we have no use for it.</para></listitem>
 </varlistentry>
 </variablelist>
 

Modified: branches/testing/BOOK/chapter05/gettext.xml
===================================================================
--- branches/testing/BOOK/chapter05/gettext.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/gettext.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -38,8 +38,8 @@
 <varlistentry>
 <term><parameter>--disable-libasprintf</parameter></term>
 <listitem><para>This flag tells Gettext not to build the
-<filename>asprintf</filename> library. Because nothing in this chapter
-or the next requires this library and Gettext gets rebuilt later,
+<filename class="libraryfile">asprintf</filename> library. Because nothing in this 
+chapter or the next requires this library and Gettext gets rebuilt later,
 exclude it to save time and space.</para></listitem>
 </varlistentry>
 

Modified: branches/testing/BOOK/chapter05/glibc.xml
===================================================================
--- branches/testing/BOOK/chapter05/glibc.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/glibc.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -31,7 +31,7 @@
 optimization flags (including the <parameter>-march</parameter> and
 <parameter>-mcpu</parameter> options) are changed. If any environment
 variables that override default optimizations have been defined, such
-as <emphasis>CFLAGS</emphasis> and <emphasis>CXXFLAGS</emphasis>,
+as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>,
 unset them when building Glibc.</para>
 
 <para>It should be noted that compiling Glibc in any way other than
@@ -147,7 +147,7 @@
 <screen><userinput>make check</userinput></screen>
 
 <para>For a discussion of test failures that are of particular
-importance, please see <xref linkend="ch-system-glibc"/>.</para>
+importance, please see <xref linkend="ch-system-glibc" role="."/></para>
 
 <para>In this chapter, some tests can be adversely effected by
 existing tools or environmental issues on the host system. Glibc test
@@ -164,8 +164,8 @@
 output so that the log file can be examined for failures later.</para>
 
 <para>The install stage of Glibc will issue a harmless warning at the
-end about the absence of /tools/etc/ld.so.conf. Prevent this warning
-with:</para>
+end about the absence of <filename>/tools/etc/ld.so.conf</filename>. 
+Prevent this warning with:</para>
 
 <screen><userinput>mkdir /tools/etc
 touch /tools/etc/ld.so.conf</userinput></screen>
@@ -199,7 +199,7 @@
 are a number of locales that are essential in order for the tests of
 future packages to pass, in particular, the
 <emphasis>libstdc++</emphasis> tests from GCC. The following
-instructions, instead of the <emphasis>install-locales</emphasis>
+instructions, instead of the <parameter>install-locales</parameter>
 target used above, will install the minimum set of locales necessary
 for the tests to run successfully:</para>
 

Modified: branches/testing/BOOK/chapter05/introduction.xml
===================================================================
--- branches/testing/BOOK/chapter05/introduction.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/introduction.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -55,8 +55,8 @@
 be used by later commands. Pay special attention to these
 reminders.</para>
 
-<para>Check one last time that the LFS environment variable is set up
-properly:</para>
+<para>Check one last time that the <envar>LFS</envar> environment 
+variable is set up properly:</para>
 
 <screen><userinput>echo $LFS</userinput></screen>
 

Modified: branches/testing/BOOK/chapter05/kernel-headers.xml
===================================================================
--- branches/testing/BOOK/chapter05/kernel-headers.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/kernel-headers.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -45,7 +45,8 @@
 <emphasis>each</emphasis> kernel compilation. Do not assume that the
 source tree is automatically clean after un-tarring.</para>
 
-<para>Create the <filename>include/linux/version.h</filename> file:</para>
+<para>Create the <filename class="headerfile">include/linux/version.h</filename>
+file:</para>
 
 <screen><userinput>make include/linux/version.h</userinput></screen>
 

Modified: branches/testing/BOOK/chapter05/m4.xml
===================================================================
--- branches/testing/BOOK/chapter05/m4.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/m4.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-m4" xreflabel="M4" role="wrap">
+<sect1 id="ch-tools-m4" role="wrap">
 <title>M4-&m4-version;</title>
 <?dbhtml filename="m4.html"?>
 

Modified: branches/testing/BOOK/chapter05/tcl.xml
===================================================================
--- branches/testing/BOOK/chapter05/tcl.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/tcl.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-tools-tcl" xreflabel="Tcl" role="wrap">
+<sect1 id="ch-tools-tcl" role="wrap">
 <title>Tcl-&tcl-version;</title>
 <?dbhtml filename="tcl.html"?>
 
@@ -29,8 +29,7 @@
 <sect2 role="installation">
 <title>Installation of Tcl</title>
 
-<para>This package and the next two (Expect and DejaGNU)
-are
+<para>This package and the next two (Expect and DejaGNU) are
 installed to support running the test suites for GCC and Binutils.
 Installing three packages for testing purposes may seem excessive, but
 it is very reassuring, if not essential, to know that the most
@@ -56,7 +55,7 @@
 the time zone to Coordinated Universal Time (UTC), also known as
 Greenwich Mean Time (GMT), but only for the duration of the test suite
 run. This ensures that the clock tests are exercised correctly. More
-information on the TZ environment variable is provided in <xref
+information on the <envar>TZ</envar> environment variable is provided in <xref
 linkend="chapter-bootscripts"/>.</para>
 
 <para>Install the package:</para>

Modified: branches/testing/BOOK/chapter05/toolchaintechnotes.xml
===================================================================
--- branches/testing/BOOK/chapter05/toolchaintechnotes.xml	2004-09-05 10:11:18 UTC (rev 4130)
+++ branches/testing/BOOK/chapter05/toolchaintechnotes.xml	2004-09-05 11:18:43 UTC (rev 4131)
@@ -39,9 +39,9 @@
 dynamic linker provided by Glibc finds and loads the shared libraries
 needed by a program, prepares the program to run, and then runs it.
 The name of the dynamic linker will usually be
-<filename>ld-linux.so.2</filename>. On platforms that are less
-prevalent, the name might be <filename>ld.so.1</filename>, and newer
-64 bit platforms might be named something else entirely. The name of
+<filename class="libraryfile">ld-linux.so.2</filename>. On platforms that are less
+prevalent, the name might be <filename class="libraryfile">ld.so.1</filename>, 
+and newer 64 bit platforms might be named something else entirely. The name of
 the platform's dynamic linker can be determined by looking in the
 <filename class="directory">/lib</filename> directory on the host
 system. A sure-fire way to determine the name is to inspect a random
@@ -86,8 +86,8 @@
 one location are hard linked to the other. An important facet of the
 linker is its library search order. Detailed information can be
 obtained from <command>ld</command> by passing it the
-<parameter>--verbose</parameter> flag. For example, an <command>ld
---verbose | grep SEARCH</command> will illustrate the current search
+<parameter>--verbose</parameter> flag. For example, an <userinput>ld
+--verbose | grep SEARCH</userinput> will illustrate the current search
 paths and their order. It shows which files are linked by
 <command>ld</command> by compiling a dummy program and passing the
 <parameter>--verbose</parameter> switch to the linker. For example,
@@ -119,7 +119,8 @@
 <para>The next package installed is Glibc. The most important
 considerations for building Glibc are the compiler, binary tools, and
 kernel headers. The compiler is generally not an issue since Glibc
-will always use the <command>gcc</command> found in a PATH directory.
+will always use the <command>gcc</command> found in a 
+<envar>PATH</envar> directory.
 The binary tools and kernel headers can be a bit more complicated.
 Therefore, take no risks and use the available configure switches to
 enforce the correct selections. After the run of




More information about the lfs-book mailing list