aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/binutils-pass2.xml
diff options
context:
space:
mode:
authorManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-12-20 16:38:42 +0000
committerManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-12-20 16:38:42 +0000
commit67906555169af493bc63114cfd1a38667dda09f5 (patch)
treeaf81b6abdaf8d7430d21ea6b94ed4ba13f1f1e02 /chapter05/binutils-pass2.xml
parentfaf339809307b5793dbd1d5891e8270d26394037 (diff)
Removed text in chapter 05 - first round.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4431 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/binutils-pass2.xml')
-rw-r--r--chapter05/binutils-pass2.xml35
1 files changed, 0 insertions, 35 deletions
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml
index 0a1799235..7491346ed 100644
--- a/chapter05/binutils-pass2.xml
+++ b/chapter05/binutils-pass2.xml
@@ -40,29 +40,10 @@ cd ../binutils-build</userinput></screen>
<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>
-
-<variablelist>
-<varlistentry>
-<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 <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>
-</variablelist>
-
-<para>Before starting to build Binutils, remember to unset any environment
-variables that override the default optimization flags.</para>
-
<para>Compile the package:</para>
<screen><userinput>make</userinput></screen>
-<para>Compilation is now complete. As discussed earlier, running the test suite
-isn't mandatory for the temporary tools here in this chapter. If you do want to
-run the Binutils test suite though, the following command will do so:</para>
-
<screen><userinput>make -k check</userinput></screen>
<para>Except for a few known failures, the binutils tests should all pass. The
@@ -72,17 +53,6 @@ exceptions to this rule are as follows:</para>
* 1 FAIL for selective4
* 1 FAIL for selective5</computeroutput></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 GCC package. However, if a failure occurs here, it should be easy
-to spot. The output shown will contain something like:</para>
-
-<blockquote><screen><computeroutput>make[1]: *** [check-binutils] Error 2</computeroutput></screen></blockquote>
-
--->
-
<para>And install the package:</para>
<screen><userinput>make install</userinput></screen>
@@ -98,11 +68,6 @@ make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen>
build directories. You will need these directories again in the next chapter
in the state they are in now.</para></warning>
-
-</sect2>
-
-<sect2 role="content"><title/>
-<para>The details on this package are found in <xref linkend="contents-binutils"/>.</para>
</sect2>
</sect1>