blob: 0a1799235907eae626cec781e86e30fb44132adb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../general.ent">
%general-entities;
]>
<sect1 id="ch-tools-binutils-pass2" role="wrap">
<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/>
<segmentedlist>
<segtitle>&buildtime;</segtitle>
<segtitle>&diskspace;</segtitle>
<seglistitem><seg>1.5 SBU</seg><seg>108 MB</seg></seglistitem>
</segmentedlist>
</sect2>
<sect2 role="installation">
<title>Re-installation of Binutils</title>
<para>The current version of Binutils in use has a bug that causes strip to
remove necessary information from certain library files. This patch fixes
the problem:</para>
<screen><userinput>patch -Np1 -i ../binutils-&binutils-version;-fix_strip-1.patch</userinput></screen>
<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>
<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
exceptions to this rule are as follows:</para>
<screen><computeroutput>* 5 FAIL (unexpected failure) for visibility
* 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>
<para>Now prepare the linker for the <quote>Re-adjusting</quote> phase in the next
chapter:</para>
<screen><userinput>make -C ld clean
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>
</sect2>
<sect2 role="content"><title/>
<para>The details on this package are found in <xref linkend="contents-binutils"/>.</para>
</sect2>
</sect1>
|
