Tagging corrections in chapters 5.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3730 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 12 insertions, 12 deletions

diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index a9e08a20b..7b5130376 100644
--- a/chapter05/gcc-pass2.xml
+++ b/chapter05/gcc-pass2.xml
@@ -30,14 +30,14 @@ them against the new Glibc, and test them properly (if running the test suites
 in this chapter). One thing to note, however, is that these test suites are
 highly dependent on properly functioning pseudo terminals (PTYs) which are
 provided by your host. These days, PTYs are most commonly implemented via the
-<emphasis>devpts</emphasis> file system. You can quickly check if your host
+<systemitem class="filesystem">devpts</systemitem> file system. You can quickly check if your host
 system is set up correctly in this regard by performing a simple test:</para>
 
 <screen><userinput>expect -c "spawn ls"</userinput></screen>
 
 <para>The response might be:</para>
 
-<blockquote><screen>The system has no more ptys.  Ask your system administrator to create more.</screen></blockquote>
+<blockquote><screen><computeroutput>The system has no more ptys.  Ask your system administrator to create more.</computeroutput></screen></blockquote>
 
 <para>If you receive the above message, your host doesn't have its PTYs set up
 properly. In this case there is no point in running the test suites for GCC
@@ -48,17 +48,17 @@ working.</para>
 <para>This time we will build both the C and the C++ compilers, so you'll have
 to unpack both the core and the g++ tarballs (and testsuite too, if you want to
 run the tests). Unpacking them in your working directory, they will all unfold
-into a single <filename>gcc-&gcc-version;/</filename> subdirectory.</para>
+into a single <filename class="directory">gcc-&gcc-version;/</filename> subdirectory.</para>
 
 <para>First correct a problem and make an essential adjustment:</para>
 
 <screen><userinput>patch -Np1 -i ../gcc-&gcc-short-version;-no-fixincludes-1.patch
 patch -Np1 -i ../gcc-&gcc-short-version;-specs-1.patch</userinput></screen>
 
-<para>The first patch disables the GCC <quote>fixincludes</quote> script. We
+<para>The first patch disables the GCC <command>fixincludes</command> script. We
 mentioned this briefly earlier, but a slightly more in-depth explanation of
 the fixincludes process is warranted here. Under normal circumstances, the GCC
-fixincludes script scans your system for header files that need to be fixed. It
+<command>fixincludes</command> 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="chapter-building-system"/>, after we've installed the newer
@@ -98,7 +98,7 @@ variables that override the default optimization flags.</para>
 
 <variablelist>
 <varlistentry>
-<term><userinput>--enable-clocale=gnu</userinput></term>
+<term><parameter>--enable-clocale=gnu</parameter></term>
 <listitem><para>This option
 ensures the correct locale model is selected for the C++ libraries under all
 circumstances. If the configure script finds the <emphasis>de_DE</emphasis>
@@ -109,13 +109,13 @@ would run the risk of building ABI incompatible C++ libraries due to the wrong
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--enable-threads=posix</userinput></term>
+<term><parameter>--enable-threads=posix</parameter></term>
 <listitem><para>This enables
 C++ exception handling for multi-threaded code.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--enable-__cxa_atexit</userinput></term>
+<term><parameter>--enable-__cxa_atexit</parameter></term>
 <listitem><para>This option
 allows use of __cxa_atexit, rather than atexit, to register C++ destructors for
 local statics and global objects and is essential for fully standards-compliant
@@ -125,13 +125,13 @@ distributions.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--enable-languages=c,c++</userinput></term>
+<term><parameter>--enable-languages=c,c++</parameter></term>
 <listitem><para>This option
 ensures that both the C and C++ compilers are built.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--disable-libstdcxx-pch</userinput></term>
+<term><parameter>--disable-libstdcxx-pch</parameter></term>
 <listitem><para>Don't build the
 PCH (pre-compiled header) for libstdc++. It takes up a ton of space, and we
 have no use for it.</para></listitem>
@@ -142,7 +142,7 @@ have no use for it.</para></listitem>
 
 <screen><userinput>make</userinput></screen>
 
-<para>There is no need to use the <emphasis>bootstrap</emphasis> target now,
+<para>There is no need to use the <parameter>bootstrap</parameter> target now,
 as the compiler we're using to compile this GCC was built from the exact same
 version of the GCC sources we used earlier.</para>
 
@@ -153,7 +153,7 @@ so:</para>
 
 <screen><userinput>make -k check</userinput></screen>
 
-<para>The <emphasis>-k</emphasis> flag is used to make the test suite run
+<para>The <parameter>-k</parameter> flag is used to make the test suite run
 through to completion and not stop at the first failure. The GCC test suite is
 very comprehensive and is almost guaranteed to generate a few failures. To get
 a summary of the test suite results, run this:</para>