Tagging corrections in chapters 5.

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

1 files changed, 14 insertions, 14 deletions

diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml
index d32b00034..df76dfa1d 100644
--- a/chapter05/glibc.xml
+++ b/chapter05/glibc.xml
@@ -28,8 +28,8 @@
 <title>Installation of Glibc</title>
 
 <para>This package is known to behave badly when you change its default
-optimization flags (including the <emphasis>-march</emphasis> and
-<emphasis>-mcpu</emphasis> options). Therefore, if you have defined any
+optimization flags (including the <parameter>-march</parameter> and
+<parameter>-mcpu</parameter> options). Therefore, if you have defined any
 environment variables that override default optimizations, such as CFLAGS and
 CXXFLAGS, we recommend un-setting them when building Glibc.</para>
 
@@ -53,40 +53,40 @@ cd ../glibc-build</userinput></screen>
 
 <variablelist>
 <varlistentry>
-<term><userinput>--disable-profile</userinput></term>
+<term><parameter>--disable-profile</parameter></term>
 <listitem><para>This builds the
 libraries without profiling information. Omit this option if you plan to do
 profiling on the temporary tools.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--enable-add-ons=nptl</userinput></term>
+<term><parameter>--enable-add-ons=nptl</parameter></term>
 <listitem><para>This tells Glibc to use the NPTL add-on as its threading 
 library.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--with-tls</userinput></term>
+<term><parameter>--with-tls</parameter></term>
 <listitem><para>This tells Glibc to include support for TLS (thread-local storage).
 This is required for NPTL to work. </para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--with-binutils=/tools/bin</userinput></term>
+<term><parameter>--with-binutils=/tools/bin</parameter></term>
 <listitem><para>Strictly speaking this switch is not required. But it does ensure 
 nothing can go wrong with regard to what Binutils programs get used during the 
 Glibc build.</para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--without-gd</userinput></term>
+<term><parameter>--without-gd</parameter></term>
 <listitem><para>This prevents the build of the <command>memusagestat</command>
 program, which strangely enough insists on linking against the host's libraries 
 (libgd, libpng, libz, and so forth). </para></listitem>
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--without-cvs</userinput></term>
+<term><parameter>--without-cvs</parameter></term>
 <listitem><para>This is meant to prevent
 the Makefiles from attempting automatic CVS checkouts when using a CVS
 snapshot. But it's not actually needed these days. We use it because it
@@ -95,7 +95,7 @@ suppresses an annoying but harmless warning about a missing
 </varlistentry>
 
 <varlistentry>
-<term><userinput>--with-headers=/tools/glibc-kernheaders</userinput></term>
+<term><parameter>--with-headers=/tools/glibc-kernheaders</parameter></term>
 <listitem><para>This tells Glibc to compile against the <quote>raw</quote> 
 kernel headers, so that it knows exactly what features the kernel has, and can 
 optimize itself accordingly.  Not strictly necessary, but nice to have.</para></listitem>
@@ -104,10 +104,10 @@ optimize itself accordingly.  Not strictly necessary, but nice to have.</para></
 
 <para>During this stage you might see the following warning:</para>
 
-<blockquote><screen>configure: WARNING:
+<blockquote><screen><computeroutput>configure: WARNING:
 *** These auxiliary programs are missing or incompatible versions: msgfmt
 *** some features will be disabled.
-*** Check the INSTALL file for required versions.</screen></blockquote>
+*** Check the INSTALL file for required versions.</computeroutput></screen></blockquote>
 
 <para>The missing or incompatible <command>msgfmt</command> program is
 generally harmless, but it's believed it can sometimes cause problems when
@@ -142,12 +142,12 @@ Certain optimization settings are also known to be a factor here.</para></listit
 host system issues. The exact reasons are not yet clear.</para></listitem>
 
 <listitem><para>The <emphasis>atime</emphasis> test sometimes fails when the
-LFS partition is mounted with the <emphasis>noatime</emphasis> option, or due
+LFS partition is mounted with the <parameter>noatime</parameter> option, or due
 to other file system quirks.</para></listitem>
 
 <listitem><para>The <emphasis>shm</emphasis> test might fail when the host
-system is running the devfs file system but doesn't have the tmpfs file system
-mounted at <filename>/dev/shm</filename> due to lack of support for tmpfs in
+system is running the devfs file system but doesn't have the <systemitem class="filesystem">tmpfs</systemitem> file system
+mounted at <filename class="directory">/dev/shm</filename> due to lack of support for tmpfs in
 the kernel.</para></listitem>
 
 <listitem><para>When running on older and slower hardware, some tests might