1 | <sect1 id="ch-tools-binutils-pass2">
|
---|
2 | <title>Installing Binutils-&binutils-version; - Pass 2</title>
|
---|
3 | <?dbhtml filename="binutils-pass2.html" dir="chapter05"?>
|
---|
4 |
|
---|
5 | <screen>&buildtime; &binutils-time-tools-pass2;
|
---|
6 | &diskspace; &binutils-compsize-tools-pass2;</screen>
|
---|
7 |
|
---|
8 | &aa-binutils-down;
|
---|
9 | &aa-binutils-dep;
|
---|
10 |
|
---|
11 | <sect2><title> </title><para> </para></sect2>
|
---|
12 |
|
---|
13 | <sect2>
|
---|
14 | <title>Re-installation of Binutils</title>
|
---|
15 |
|
---|
16 | <para>Create a separate build directory again:</para>
|
---|
17 |
|
---|
18 | <screen><userinput>mkdir ../binutils-build
|
---|
19 | cd ../binutils-build</userinput></screen>
|
---|
20 |
|
---|
21 | <para>Now prepare Binutils for compilation:</para>
|
---|
22 |
|
---|
23 | <screen><userinput>../&binutils-dir;/configure --prefix=/tools \
|
---|
24 | --enable-shared --with-lib-path=/tools/lib</userinput></screen>
|
---|
25 |
|
---|
26 | <para>The meaning of the new configure option:</para>
|
---|
27 |
|
---|
28 | <itemizedlist>
|
---|
29 | <listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells
|
---|
30 | the configure script to specify the library search path during the compilation
|
---|
31 | of Binutils, resulting in <emphasis>/tools/lib</emphasis> to be passed to the
|
---|
32 | linker. This prevents the linker from searching through library directories on
|
---|
33 | the host.</para></listitem>
|
---|
34 | </itemizedlist>
|
---|
35 |
|
---|
36 | <para>Before starting to build Binutils, remember to unset any environment
|
---|
37 | variables that override the default optimization flags.</para>
|
---|
38 |
|
---|
39 | <para>Compile the package:</para>
|
---|
40 |
|
---|
41 | <screen><userinput>make</userinput></screen>
|
---|
42 |
|
---|
43 | <para>Compilation is now complete. As discussed earlier, we don't recommend
|
---|
44 | running the test suites for the temporary tools here in this chapter. If
|
---|
45 | nevertheless you want to run the Binutils test suite, the following command
|
---|
46 | will do so:</para>
|
---|
47 |
|
---|
48 | <screen><userinput>make check</userinput></screen>
|
---|
49 |
|
---|
50 | <para>There should be no unexpected failures here, expected failures are fine.
|
---|
51 | Unfortunately, there is no easy way to view the test results summary like there
|
---|
52 | was for the GCC package. However, if a failure occurs here, it should be easy
|
---|
53 | to spot. The output shown will contain something like:</para>
|
---|
54 |
|
---|
55 | <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote>
|
---|
56 |
|
---|
57 | <para>And install the package:</para>
|
---|
58 |
|
---|
59 | <screen><userinput>make install</userinput></screen>
|
---|
60 |
|
---|
61 | <para>Now prepare the linker for the "Re-adjusting" phase in the next
|
---|
62 | chapter:</para>
|
---|
63 |
|
---|
64 | <screen><userinput>make -C ld clean
|
---|
65 | make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen>
|
---|
66 |
|
---|
67 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
68 | <literallayout></literallayout>
|
---|
69 |
|
---|
70 | <warning><para><emphasis>Do not yet remove</emphasis> the Binutils source and
|
---|
71 | build directories. You will need these directories again in the next chapter
|
---|
72 | in the state they are in now.</para></warning>
|
---|
73 |
|
---|
74 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
75 | <literallayout></literallayout>
|
---|
76 |
|
---|
77 | </sect2>
|
---|
78 |
|
---|
79 | <sect2><title> </title><para> </para>
|
---|
80 | <para>The details on this package are found in <xref linkend="contents-binutils"/>.</para>
|
---|
81 | <para> </para></sect2>
|
---|
82 |
|
---|
83 | </sect1>
|
---|
84 |
|
---|