diff options
author | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-09 23:22:07 +0000 |
---|---|---|
committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-09 23:22:07 +0000 |
commit | 21ba4e3570c1c2524b0733d492ced9634b259353 (patch) | |
tree | f5124d2e6106d2e29e5b32f79b56a90defabdbd9 /chapter05/binutils-pass2-inst.xml | |
parent | 1a7aecc6119f540e24a4e8da1b583a625b5690c1 (diff) |
Internal markup reworking to fix the extraneous whitespace problem in the "tidy generated" web site pages. Essentially replace all ocurrences of <para><screen> with <screen> (and of course the matching closing tags).
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2958 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/binutils-pass2-inst.xml')
-rw-r--r-- | chapter05/binutils-pass2-inst.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/chapter05/binutils-pass2-inst.xml b/chapter05/binutils-pass2-inst.xml index 7b46d7ce8..901f89ed1 100644 --- a/chapter05/binutils-pass2-inst.xml +++ b/chapter05/binutils-pass2-inst.xml @@ -9,13 +9,13 @@ section is considered not as important as the one we run in Chapter 6.</para> <para>Create a separate build directory again:</para> -<para><screen><userinput>mkdir ../binutils-build -cd ../binutils-build</userinput></screen></para> +<screen><userinput>mkdir ../binutils-build +cd ../binutils-build</userinput></screen> <para>Now prepare Binutils to be compiled:</para> -<para><screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \ - --enable-shared --with-lib-path=/tools/lib</userinput></screen></para> +<screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \ + --enable-shared --with-lib-path=/tools/lib</userinput></screen> <para>The meaning of the new configure option:</para> @@ -31,12 +31,12 @@ variables that override the default optimization flags.</para> <para>Compile the package:</para> -<para><screen><userinput>make </userinput></screen></para> +<screen><userinput>make </userinput></screen> <para>Test the results (there should be no unexpected failures here, expected failures are fine):</para> -<para><screen><userinput>make check</userinput></screen></para> +<screen><userinput>make check</userinput></screen> <para>Unfortunately, there is no easy way to view the test results summary like there was for the previous GCC package. However, if a failure occurs here, it @@ -46,13 +46,13 @@ should be easy to spot. The output shown will contain something like:</para> <para>And install the package:</para> -<para><screen><userinput>make install</userinput></screen></para> +<screen><userinput>make install</userinput></screen> <para>Now prepare Binutils for the re-adjusting of the toolchain in the next chapter:</para> -<para><screen><userinput>make -C ld clean -make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen></para> +<screen><userinput>make -C ld clean +make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen> <warning><para>Do not yet remove the Binutils source and build directories. We'll need these directories again in the next chapter in the state they are in |