From 3c928f1c576bdc82b3dab964a575ba5bd56b15bf Mon Sep 17 00:00:00 2001
From: Manuel Canales Esparcia <manuel@linuxfromscratch.org>
Date: Sun, 13 Jun 2004 12:58:23 +0000
Subject: Added a separate file for the strippingagain section. Tags
 correcitions.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3780 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter06/binutils.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'chapter06/binutils.xml')

diff --git a/chapter06/binutils.xml b/chapter06/binutils.xml
index b05d0416e..75421eb41 100644
--- a/chapter06/binutils.xml
+++ b/chapter06/binutils.xml
@@ -37,14 +37,14 @@ everything is set up correctly by performing a simple test:</para>
 
 <para>If you receive the message:</para>
 
-<blockquote><screen>The system has no more ptys.  Ask your system administrator to create more.</screen></blockquote>
+<screen><computeroutput>The system has no more ptys.  Ask your system administrator to create more.</computeroutput></screen>
 
 <para>Your chroot environment is not set up for proper PTY operation. In this
 case there is no point in running the test suites for Binutils and GCC until you
 are able to resolve the issue.</para>
 
 <para>This package is known to behave badly when you have changed its
-default optimization flags (including the -march and -mcpu options).
+default 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
 or modifying them when building Binutils.</para>
@@ -65,9 +65,9 @@ cd ../binutils-build</userinput></screen>
 
 <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
 executables end up) is set to $(exec_prefix)/$(target_alias), which expands
-into, for example, <filename>/usr/i686-pc-linux-gnu</filename>. Since we only
+into, for example, <filename class="directory">/usr/i686-pc-linux-gnu</filename>. Since we only
 build for our own system, we don't need this target specific directory in
-<filename>/usr</filename>. That setup would be used if the system was used to
+<filename class="directory">/usr</filename>. That setup would be used if the system was used to
 cross-compile (for example compiling a package on an Intel machine that
 generates code that can be executed on PowerPC machines).</para>
 
@@ -87,7 +87,7 @@ doubts.</para>
 
 <screen><userinput>make tooldir=/usr install</userinput></screen>
 
-<para>Install the <emphasis>libiberty</emphasis> header file that is needed by
+<para>Install the <filename class="headerfile">libiberty</filename> header file that is needed by
 some packages:</para>
 
 <screen><userinput>cp ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen>
@@ -133,7 +133,7 @@ the archive).</para>
 <term><command>as</command></term>
 <listitem>
 <indexterm zone="ch-system-binutils as"><primary sortas="b-as">as</primary></indexterm>
-<para>is an assembler. It assembles the output of gcc into object files.</para>
+<para>is an assembler. It assembles the output of <command>gcc</command> into object files.</para>
 </listitem>
 </varlistentry>
 
-- 
cgit v1.2.3-54-g00ecf