diff options
author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2005-02-19 22:16:42 +0000 |
---|---|---|
committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2005-02-19 22:16:42 +0000 |
commit | 81fd230419b0cfd052b08fc1ed352bb7d49975df (patch) | |
tree | 24c98d2876e5b457dcb88d39e7cca4905f58691a /chapter05/binutils-pass2.xml | |
parent | 2f9131f8390243dbc350fe2eeb9e1d58f0264888 (diff) |
Trunk is now identical to Testing
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4648 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/binutils-pass2.xml')
-rw-r--r-- | chapter05/binutils-pass2.xml | 63 |
1 files changed, 47 insertions, 16 deletions
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml index 0c28271f7..85a574309 100644 --- a/chapter05/binutils-pass2.xml +++ b/chapter05/binutils-pass2.xml @@ -7,7 +7,14 @@ <title>Binutils-&binutils-version; - Pass 2</title> <?dbhtml filename="binutils-pass2.html"?> +<indexterm zone="ch-tools-binutils-pass2"> +<primary sortas="a-Binutils">Binutils</primary> +<secondary>tools, pass 2</secondary></indexterm> + <sect2 role="package"><title/> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" + href="../chapter06/binutils.xml" + xpointer="xpointer(/sect1/sect2[1]/para[1])"/> <segmentedlist> <segtitle>&buildtime;</segtitle> @@ -15,39 +22,57 @@ <seglistitem><seg>1.5 SBU</seg><seg>108 MB</seg></seglistitem> </segmentedlist> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" + href="../chapter06/binutils.xml" + xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> + </sect2> <sect2 role="installation"> <title>Re-installation of Binutils</title> +<para>This package is known to have issues when its default +optimization flags (including the <parameter>-march</parameter> and +<parameter>-mcpu</parameter> options) are changed. If any environment +variables that override default optimizations have been defined, such +as <envar>CFLAGS</envar> and <envar>CXXFLAGS</envar>, +unset them when building Binutils.</para> + <para>Create a separate build directory again:</para> <screen><userinput>mkdir ../binutils-build cd ../binutils-build</userinput></screen> -<para>Now prepare Binutils for compilation:</para> +<para>Prepare Binutils for compilation:</para> <screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \ --enable-shared --with-lib-path=/tools/lib</userinput></screen> -<para>Compile the package:</para> +<para>The meaning of the new configure option:</para> -<screen><userinput>make</userinput></screen> +<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 <filename +class="directory">/tools/lib</filename> being passed to the linker. +This prevents the linker from searching through library directories on +the host.</para></listitem> +</varlistentry> +</variablelist> -<para>Test the results:</para> +<para>Compile the package:</para> -<!-- NEW --> -<screen><userinput>make -k check</userinput></screen> +<screen><userinput>make</userinput></screen> -<para>Except for a few known failures, the binutils tests should all pass. The -exceptions to this rule are as follows:</para> +<para>Compilation is now complete. As discussed earlier, running the +test suite is not mandatory for the temporary tools here in this +chapter. To run the Binutils test suite anyway, issue the following +command:</para> -<screen><computeroutput>* 5 FAIL (unexpected failure) for visibility -* 1 FAIL for selective4 -* 1 FAIL for selective5</computeroutput></screen> -<!-- END NEW--> +<screen><userinput>make check</userinput></screen> -<para>And install the package:</para> +<para>Install the package:</para> <screen><userinput>make install</userinput></screen> @@ -58,10 +83,16 @@ chapter:</para> make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen> -<warning><para><emphasis>Do not yet remove</emphasis> the Binutils source and -build directories. You will need these directories again in the next chapter -in the state they are in now.</para></warning> +<warning><para><emphasis>Do not</emphasis> remove the Binutils source and +build directories yet. These directories will be needed again in the next +chapter in their current state.</para></warning> </sect2> +<sect2 role="content"><title/> +<para>Details on this package are located in <xref +linkend="contents-binutils" role="."/></para> +</sect2> + </sect1> + |