[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
[9652249] | 6 | <sect1 id="ch-tools-binutils-pass2" role="wrap">
|
---|
[673b0d8] | 7 | <title>Binutils-&binutils-version; - Pass 2</title>
|
---|
| 8 | <?dbhtml filename="binutils-pass2.html"?>
|
---|
[bc82645e] | 9 |
|
---|
[673b0d8] | 10 | <indexterm zone="ch-tools-binutils-pass2">
|
---|
| 11 | <primary sortas="a-Binutils">Binutils</primary>
|
---|
| 12 | <secondary>tools, pass 2</secondary></indexterm>
|
---|
[bc82645e] | 13 |
|
---|
[9652249] | 14 | <sect2 role="package"><title/>
|
---|
[5888299] | 15 |
|
---|
[9652249] | 16 | <segmentedlist>
|
---|
| 17 | <segtitle>&buildtime;</segtitle>
|
---|
| 18 | <segtitle>&diskspace;</segtitle>
|
---|
| 19 | <seglistitem><seg>1.5 SBU</seg><seg>108 MB</seg></seglistitem>
|
---|
| 20 | </segmentedlist>
|
---|
[73aedd1d] | 21 |
|
---|
[9652249] | 22 | </sect2>
|
---|
| 23 |
|
---|
| 24 | <sect2 role="installation">
|
---|
[73aedd1d] | 25 | <title>Re-installation of Binutils</title>
|
---|
| 26 |
|
---|
[af133c3] | 27 | <para>The current version of Binutils in use has a bug that causes strip to
|
---|
| 28 | remove necessary information from certain library files. This patch fixes
|
---|
| 29 | the problem:</para>
|
---|
| 30 |
|
---|
| 31 | <screen><userinput>patch -Np1 -i ../binutils-&binutils-version;-fix_strip-1.patc
|
---|
| 32 | h</userinput></screen>
|
---|
| 33 |
|
---|
[73aedd1d] | 34 | <para>Create a separate build directory again:</para>
|
---|
| 35 |
|
---|
| 36 | <screen><userinput>mkdir ../binutils-build
|
---|
| 37 | cd ../binutils-build</userinput></screen>
|
---|
| 38 |
|
---|
[d27a27b] | 39 | <para>Now prepare Binutils for compilation:</para>
|
---|
[73aedd1d] | 40 |
|
---|
[673b0d8] | 41 | <screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \
|
---|
| 42 | --enable-shared --with-lib-path=/tools/lib</userinput></screen>
|
---|
[73aedd1d] | 43 |
|
---|
| 44 | <para>The meaning of the new configure option:</para>
|
---|
| 45 |
|
---|
[9652249] | 46 | <variablelist>
|
---|
| 47 | <varlistentry>
|
---|
[574b0ea] | 48 | <term><parameter>--with-lib-path=/tools/lib</parameter></term>
|
---|
[9652249] | 49 | <listitem><para>This tells the configure script to specify the library search path
|
---|
[574b0ea] | 50 | during the compilation of Binutils, resulting in <parameter>/tools/lib</parameter>
|
---|
[9652249] | 51 | to be passed to the linker. This prevents the linker from searching through library
|
---|
| 52 | directories on the host.</para></listitem>
|
---|
| 53 | </varlistentry>
|
---|
| 54 | </variablelist>
|
---|
[73aedd1d] | 55 |
|
---|
| 56 | <para>Before starting to build Binutils, remember to unset any environment
|
---|
| 57 | variables that override the default optimization flags.</para>
|
---|
| 58 |
|
---|
| 59 | <para>Compile the package:</para>
|
---|
| 60 |
|
---|
[b3adaba] | 61 | <screen><userinput>make</userinput></screen>
|
---|
[73aedd1d] | 62 |
|
---|
[d878ce3] | 63 | <para>Compilation is now complete. As discussed earlier, running the test suite
|
---|
| 64 | isn't mandatory for the temporary tools here in this chapter. If you do want to
|
---|
| 65 | run the Binutils test suite though, the following command will do so:</para>
|
---|
[73aedd1d] | 66 |
|
---|
[9dfc02f] | 67 | <screen><userinput>make -k check</userinput></screen>
|
---|
| 68 |
|
---|
| 69 | <para>Except for a few known failures, the binutils tests should all pass. The
|
---|
| 70 | exceptions to this rule are as follows:</para>
|
---|
| 71 |
|
---|
[574b0ea] | 72 | <screen><computeroutput>* 5 FAIL (unexpected failure) for visibility
|
---|
[9dfc02f] | 73 | * 1 FAIL for selective4
|
---|
[574b0ea] | 74 | * 1 FAIL for selective5</computeroutput></screen>
|
---|
[9dfc02f] | 75 |
|
---|
| 76 | <!--
|
---|
[73aedd1d] | 77 |
|
---|
[443cace] | 78 | <para>There should be no unexpected failures here, expected failures are fine.
|
---|
[ede9b9b] | 79 | Unfortunately, there is no easy way to view the test results summary like there
|
---|
| 80 | was for the GCC package. However, if a failure occurs here, it should be easy
|
---|
| 81 | to spot. The output shown will contain something like:</para>
|
---|
[73aedd1d] | 82 |
|
---|
[574b0ea] | 83 | <blockquote><screen><computeroutput>make[1]: *** [check-binutils] Error 2</computeroutput></screen></blockquote>
|
---|
[73aedd1d] | 84 |
|
---|
[9dfc02f] | 85 | -->
|
---|
| 86 |
|
---|
[17476c5] | 87 | <para>And install the package:</para>
|
---|
[73aedd1d] | 88 |
|
---|
| 89 | <screen><userinput>make install</userinput></screen>
|
---|
| 90 |
|
---|
[574b0ea] | 91 | <para>Now prepare the linker for the <quote>Re-adjusting</quote> phase in the next
|
---|
[73aedd1d] | 92 | chapter:</para>
|
---|
| 93 |
|
---|
| 94 | <screen><userinput>make -C ld clean
|
---|
| 95 | make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen>
|
---|
| 96 |
|
---|
| 97 |
|
---|
[a0b689e] | 98 | <warning><para><emphasis>Do not yet remove</emphasis> the Binutils source and
|
---|
| 99 | build directories. You will need these directories again in the next chapter
|
---|
| 100 | in the state they are in now.</para></warning>
|
---|
[73aedd1d] | 101 |
|
---|
| 102 |
|
---|
| 103 | </sect2>
|
---|
[bc82645e] | 104 |
|
---|
[9652249] | 105 | <sect2 role="content"><title/>
|
---|
[5888299] | 106 | <para>The details on this package are found in <xref linkend="contents-binutils"/>.</para>
|
---|
[0868461] | 107 | </sect2>
|
---|
[5888299] | 108 |
|
---|
[bc82645e] | 109 | </sect1>
|
---|