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, 9 insertions, 9 deletions

diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index 2be683d55..2dccf00f6 100644
--- a/chapter05/gcc-pass2.xml
+++ b/chapter05/gcc-pass2.xml
@@ -53,7 +53,7 @@
     to see if the host system is set up correctly in this regard by
     performing a quick test:</para>
 
-<screen><userinput>expect -c "spawn ls"</userinput></screen>
+<screen><userinput remap="test">expect -c "spawn ls"</userinput></screen>
 
     <para>The response might be:</para>
 
@@ -77,7 +77,7 @@ Ask your system administrator to create more.</computeroutput></screen>
     directory. The running of the <command>fixincludes</command> script can
     be suppressed by issuing the following commands:</para>
 
-<screen><userinput>cp -v gcc/Makefile.in{,.orig}
+<screen><userinput remap="pre">cp -v gcc/Makefile.in{,.orig}
 sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
 
     <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>
@@ -86,7 +86,7 @@ sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig &gt; gcc/Makefile.in</userin
     <command>sed</command> to use it in order to ensure consistent compiler
     builds:</para>
 
-<screen><userinput>cp -v gcc/Makefile.in{,.tmp}
+<screen><userinput remap="pre">cp -v gcc/Makefile.in{,.tmp}
 sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
   &gt; gcc/Makefile.in</userinput></screen>
 
@@ -99,7 +99,7 @@ sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
     GCC. That is, all of the binaries created during the build will link
     against the new Glibc. Issue:</para>
 
-<screen><userinput>for file in $(find gcc/config -name linux64.h -o -name linux.h)
+<screen><userinput remap="pre">for file in $(find gcc/config -name linux64.h -o -name linux.h)
 do
   cp -uv $file{,.orig}
   sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&amp;@g' \
@@ -126,7 +126,7 @@ done</userinput></screen>
 
     <para>Create a separate build directory again:</para>
 
-<screen><userinput>mkdir -v ../gcc-build
+<screen><userinput remap="pre">mkdir -v ../gcc-build
 cd ../gcc-build</userinput></screen>
 
     <para>Before starting to build GCC, remember to unset any environment
@@ -134,7 +134,7 @@ cd ../gcc-build</userinput></screen>
 
     <para>Now prepare GCC for compilation:</para>
 
-<screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \
+<screen><userinput remap="configure">../gcc-&gcc-version;/configure --prefix=/tools \
     --with-local-prefix=/tools --enable-clocale=gnu \
     --enable-shared --enable-threads=posix \
     --enable-__cxa_atexit --enable-languages=c,c++ \
@@ -206,7 +206,7 @@ cd ../gcc-build</userinput></screen>
 
     <para>Compile the package:</para>
 
-<screen><userinput>make</userinput></screen>
+<screen><userinput remap="make">make</userinput></screen>
 
     <para>There is no need to use the <parameter>bootstrap</parameter> target
     now because the compiler being used to compile this GCC was built from
@@ -216,7 +216,7 @@ cd ../gcc-build</userinput></screen>
     suites for the temporary tools compiled in this chapter is not mandatory.
     To run the GCC test suite anyway, use the following command:</para>
 
-<screen><userinput>make -k check</userinput></screen>
+<screen><userinput remap="test">make -k check</userinput></screen>
 
     <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
@@ -228,7 +228,7 @@ cd ../gcc-build</userinput></screen>
 
     <para>Install the package:</para>
 
-<screen><userinput>make install</userinput></screen>
+<screen><userinput remap="install">make install</userinput></screen>
 
     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
     href="adjusting.xml"