Added remap attributes to userinput tags in packages pages.

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

1 files changed, 12 insertions, 12 deletions

diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml
index 842f8250b..5ea33fc97 100644
--- a/chapter06/gcc.xml
+++ b/chapter06/gcc.xml
@@ -46,7 +46,7 @@
     version of <filename class="libraryfile">libiberty.a</filename> provided by
     Binutils will be used instead:</para>
 
-<screen><userinput>sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in</userinput></screen>
+<screen><userinput remap="pre">sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in</userinput></screen>
 
     <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>
     built GCC with the <option>-fomit-frame-pointer</option> compiler flag.
@@ -54,7 +54,7 @@
     <command>sed</command> to use it in order to ensure consistent compiler
     builds:</para>
 
-<screen><userinput>sed -i 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in</userinput></screen>
+<screen><userinput remap="pre">sed -i 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in</userinput></screen>
 
     <para>The <command>fixincludes</command> script is known to occasionally
     erroneously attempt to &quot;fix&quot; the system headers installed so far. As
@@ -62,7 +62,7 @@
     to not require fixing, issue the following command to prevent the
     <command>fixincludes</command> script from running:</para>
 
-<screen><userinput>sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in</userinput></screen>
+<screen><userinput remap="pre">sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in</userinput></screen>
 
     <para>GCC provides a <command>gccbug</command> script which detects at
     compile time whether mktemp is present, and hardcodes the result in a test.
@@ -70,17 +70,17 @@
     temporary files.  We will be installing mktemp later, so the following sed
     will simulate its presence:</para>
 
-<screen><userinput>sed -i 's/@have_mktemp_command@/yes/' gcc/gccbug.in</userinput></screen>
+<screen><userinput remap="pre">sed -i 's/@have_mktemp_command@/yes/' gcc/gccbug.in</userinput></screen>
 
     <para>The GCC documentation recommends building GCC outside of the source
     directory in a dedicated build directory:</para>
 
-<screen><userinput>mkdir -v ../gcc-build
+<screen><userinput remap="pre">mkdir -v ../gcc-build
 cd ../gcc-build</userinput></screen>
 
     <para>Prepare GCC for compilation:</para>
 
-<screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
+<screen><userinput remap="configure">../gcc-&gcc-version;/configure --prefix=/usr \
     --libexecdir=/usr/lib --enable-shared \
     --enable-threads=posix --enable-__cxa_atexit \
     --enable-clocale=gnu --enable-languages=c,c++ \
@@ -88,7 +88,7 @@ cd ../gcc-build</userinput></screen>
 
     <para>Compile the package:</para>
 
-<screen><userinput>make</userinput></screen>
+<screen><userinput remap="make">make</userinput></screen>
 
     <important>
       <para>In this section, the test suite for GCC is considered
@@ -97,11 +97,11 @@ cd ../gcc-build</userinput></screen>
 
     <para>Test the results, but do not stop at errors:</para>
 
-<screen><userinput>make -k check</userinput></screen>
+<screen><userinput remap="test">make -k check</userinput></screen>
 
     <para>To receive a summary of the test suite results, run:</para>
 
-<screen><userinput>../gcc-&gcc-version;/contrib/test_summary</userinput></screen>
+<screen><userinput remap="test">../gcc-&gcc-version;/contrib/test_summary</userinput></screen>
 
     <para>For only the summaries, pipe the output through
     <userinput>grep -A7 Summ</userinput>.</para>
@@ -119,18 +119,18 @@ cd ../gcc-build</userinput></screen>
 
     <para>Install the package:</para>
 
-<screen><userinput>make install</userinput></screen>
+<screen><userinput remap="install">make install</userinput></screen>
 
     <para>Some packages expect the C preprocessor to be installed in the
     <filename class="directory">/lib</filename> directory.
     To support those packages, create this symlink:</para>
 
-<screen><userinput>ln -sv ../usr/bin/cpp /lib</userinput></screen>
+<screen><userinput remap="install">ln -sv ../usr/bin/cpp /lib</userinput></screen>
 
     <para>Many packages use the name <command>cc</command> to call the C
     compiler. To satisfy those packages, create a symlink:</para>
 
-<screen><userinput>ln -sv gcc /usr/bin/cc</userinput></screen>
+<screen><userinput remap="install">ln -sv gcc /usr/bin/cc</userinput></screen>
 
     <para>Now that our final toolchain is in place, it is important to again ensure
     that compiling and linking will work as expected. We do this by performing