diff options
| author | Alex Gronenwoud <alex@linuxfromscratch.org> | 2004-02-25 22:04:14 +0000 |
|---|---|---|
| committer | Alex Gronenwoud <alex@linuxfromscratch.org> | 2004-02-25 22:04:14 +0000 |
| commit | ede9b9be0a3baef5e7b8daaab72b5ff594ea12e7 (patch) | |
| tree | 79b8fd44df338bdfc7ecabf99240fc888d3a3cd0 /chapter05/binutils-pass2.xml | |
| parent | e421d2e1df618260a60b79f2dc97d89d16c407b8 (diff) | |
Minor textual shuffles.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3261 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/binutils-pass2.xml')
| -rw-r--r-- | chapter05/binutils-pass2.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml index b77e9dac5..2ccd0bf68 100644 --- a/chapter05/binutils-pass2.xml +++ b/chapter05/binutils-pass2.xml @@ -8,7 +8,6 @@ &aa-binutils-down; &aa-binutils-dep; - <sect2><title> </title><para> </para></sect2> <sect2> @@ -28,9 +27,10 @@ cd ../binutils-build</userinput></screen> <itemizedlist> <listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells -the configure script to specify the default library search path. We don't want -the library search path to contain library directories from the host -system.</para></listitem> +the configure script to specify the library search path during the compilation +of Binutils, resulting in <emphasis>/tools/lib</emphasis> to be passed to the +linker. This prevents the linker from searching through library directories on +the host.</para></listitem> </itemizedlist> <para>Before starting to build Binutils, remember to unset any environment @@ -41,16 +41,16 @@ variables that override the default optimization flags.</para> <screen><userinput>make</userinput></screen> <para>Compilation is now complete. As discussed earlier, we don't recommend -running the test suites for the temporary tools here in this chapter. If you -still want to run the Binutils test suite anyway, the following command will -do so:</para> +running the test suites for the temporary tools here in this chapter. If +nevertheless you want to run the Binutils test suite, the following command +will do so:</para> <screen><userinput>make check</userinput></screen> <para>There should be no unexpected failures here, expected failures are fine. -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 -should be easy to spot. The output shown will contain something like:</para> +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> |