| 1 | <sect1 id="ch05-binutils-pass2">
|
|---|
| 2 | <title>Installing Binutils-&binutils-version; - Pass 2</title>
|
|---|
| 3 | <?dbhtml filename="binutils-pass2.html" dir="chapter05"?>
|
|---|
| 4 |
|
|---|
| 5 | <screen>Estimated build time: &binutils-time-tools-pass2;
|
|---|
| 6 | Estimated required disk space: &binutils-compsize-tools-pass2;</screen>
|
|---|
| 7 |
|
|---|
| 8 |
|
|---|
| 9 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 10 |
|
|---|
| 11 | <sect2>
|
|---|
| 12 | <title>Re-installation of Binutils</title>
|
|---|
| 13 |
|
|---|
| 14 | <para>Create a separate build directory again:</para>
|
|---|
| 15 |
|
|---|
| 16 | <screen><userinput>mkdir ../binutils-build
|
|---|
| 17 | cd ../binutils-build</userinput></screen>
|
|---|
| 18 |
|
|---|
| 19 | <para>Now prepare Binutils for compilation:</para>
|
|---|
| 20 |
|
|---|
| 21 | <screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \
|
|---|
| 22 | --enable-shared --with-lib-path=/tools/lib</userinput></screen>
|
|---|
| 23 |
|
|---|
| 24 | <para>The meaning of the new configure option:</para>
|
|---|
| 25 |
|
|---|
| 26 | <itemizedlist>
|
|---|
| 27 | <listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells
|
|---|
| 28 | the configure script to specify the default library search path. We don't want
|
|---|
| 29 | the library search path to contain library directories from the host
|
|---|
| 30 | system.</para></listitem>
|
|---|
| 31 | </itemizedlist>
|
|---|
| 32 |
|
|---|
| 33 | <para>Before starting to build Binutils, remember to unset any environment
|
|---|
| 34 | variables that override the default optimization flags.</para>
|
|---|
| 35 |
|
|---|
| 36 | <para>Compile the package:</para>
|
|---|
| 37 |
|
|---|
| 38 | <screen><userinput>make</userinput></screen>
|
|---|
| 39 |
|
|---|
| 40 | <note><para>It's worth pointing out that running the Binutils test suite here
|
|---|
| 41 | is considered not as important as running it in
|
|---|
| 42 | <xref linkend="chapter06"/>.</para></note>
|
|---|
| 43 |
|
|---|
| 44 | <para>Test the results (there should be no unexpected failures here, expected
|
|---|
| 45 | failures are fine):</para>
|
|---|
| 46 |
|
|---|
| 47 | <screen><userinput>make check</userinput></screen>
|
|---|
| 48 |
|
|---|
| 49 | <para>Unfortunately, there is no easy way to view the test results summary like
|
|---|
| 50 | there was for the previous GCC package. However, if a failure occurs here, it
|
|---|
| 51 | should be easy to spot. The output shown will contain something like:</para>
|
|---|
| 52 |
|
|---|
| 53 | <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote>
|
|---|
| 54 |
|
|---|
| 55 | <para>And install the package:</para>
|
|---|
| 56 |
|
|---|
| 57 | <screen><userinput>make install</userinput></screen>
|
|---|
| 58 |
|
|---|
| 59 | <para>Now prepare Binutils for the re-adjusting of the toolchain in the next
|
|---|
| 60 | chapter:</para>
|
|---|
| 61 |
|
|---|
| 62 | <screen><userinput>make -C ld clean
|
|---|
| 63 | make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen>
|
|---|
| 64 |
|
|---|
| 65 | <!-- HACK - Force some whitespace to appease tidy -->
|
|---|
| 66 | <literallayout></literallayout>
|
|---|
| 67 |
|
|---|
| 68 | <warning><para>Do not yet remove the Binutils source and build directories.
|
|---|
| 69 | We'll need these directories again in the next chapter in the state they are in
|
|---|
| 70 | now.</para></warning>
|
|---|
| 71 |
|
|---|
| 72 | <!-- HACK - Force some whitespace to appease tidy -->
|
|---|
| 73 | <literallayout></literallayout>
|
|---|
| 74 |
|
|---|
| 75 | </sect2>
|
|---|
| 76 |
|
|---|
| 77 | </sect1>
|
|---|
| 78 |
|
|---|
