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