Changeset ede9b9b for chapter05/binutils-pass2.xml

Timestamp:

02/25/2004 10:04:14 PM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

dd3e8c6

Parents:

e421d2e

Message:

Minor textual shuffles.

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

File:

• chapter05/binutils-pass2.xml (modified) (3 diffs)

chapter05/binutils-pass2.xml

@@ -8 +8 @@
 &aa-binutils-down;
 &aa-binutils-dep;
-
 
 <sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
@@ -29 +28 @@
 <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>
 
@@ -42 +42 @@
 
 <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>