diff options
Diffstat (limited to 'chapter05/binutils-pass2.xml')
| -rw-r--r-- | chapter05/binutils-pass2.xml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml index 584fd4513..7eb1cf670 100644 --- a/chapter05/binutils-pass2.xml +++ b/chapter05/binutils-pass2.xml @@ -38,9 +38,9 @@ cd ../binutils-build</userinput></screen> <variablelist> <varlistentry> -<term><userinput>--with-lib-path=/tools/lib</userinput></term> +<term><parameter>--with-lib-path=/tools/lib</parameter></term> <listitem><para>This tells the configure script to specify the library search path -during the compilation of Binutils, resulting in <emphasis>/tools/lib</emphasis> +during the compilation of Binutils, resulting in <parameter>/tools/lib</parameter> to be passed to the linker. This prevents the linker from searching through library directories on the host.</para></listitem> </varlistentry> @@ -63,9 +63,9 @@ will do so:</para> <para>Except for a few known failures, the binutils tests should all pass. The exceptions to this rule are as follows:</para> -<screen>* 5 FAIL (unexpected failure) for visibility +<screen><computeroutput>* 5 FAIL (unexpected failure) for visibility * 1 FAIL for selective4 -* 1 FAIL for selective5</screen> +* 1 FAIL for selective5</computeroutput></screen> <!-- @@ -74,7 +74,7 @@ Unfortunately, there is no easy way to view the test results summary like there was for the GCC package. However, if a failure occurs here, it should be easy to spot. The output shown will contain something like:</para> -<blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote> +<blockquote><screen><computeroutput>make[1]: *** [check-binutils] Error 2</computeroutput></screen></blockquote> --> @@ -82,7 +82,7 @@ to spot. The output shown will contain something like:</para> <screen><userinput>make install</userinput></screen> -<para>Now prepare the linker for the "Re-adjusting" phase in the next +<para>Now prepare the linker for the <quote>Re-adjusting</quote> phase in the next chapter:</para> <screen><userinput>make -C ld clean |