2003-05-02 19:20:20 +01:00
|
|
|
<sect2><title> </title><para> </para></sect2>
|
|
|
|
|
|
|
|
<sect2>
|
2003-08-11 23:49:50 +01:00
|
|
|
<title>Re-installation of Binutils</title>
|
2003-05-02 19:20:20 +01:00
|
|
|
|
2003-09-22 15:25:37 +01:00
|
|
|
<para>Create a separate build directory again:</para>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>mkdir ../binutils-build
|
|
|
|
cd ../binutils-build</userinput></screen>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
|
|
|
<para>Now prepare Binutils to be compiled:</para>
|
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>../binutils-&binutils-version;/configure --prefix=/tools \
|
|
|
|
--enable-shared --with-lib-path=/tools/lib</userinput></screen>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-09-25 00:48:45 +01:00
|
|
|
<para>The meaning of the new configure option:</para>
|
|
|
|
|
|
|
|
<itemizedlist>
|
|
|
|
<listitem><para><userinput>--with-lib-path=/tools/lib</userinput>: This tells
|
|
|
|
the configure script to specify the default library search path. We don't want
|
|
|
|
the library search path to contain library directories from the host
|
|
|
|
system.</para></listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
|
2003-08-11 23:49:50 +01:00
|
|
|
<para>Before starting to build Binutils, remember to unset any environment
|
|
|
|
variables that override the default optimization flags.</para>
|
|
|
|
|
2003-08-09 12:45:03 +01:00
|
|
|
<para>Compile the package:</para>
|
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>make </userinput></screen>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-10-01 12:14:11 +01:00
|
|
|
<para>Test the results (there should be no unexpected failures here, expected
|
|
|
|
failures are fine):</para>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>make check</userinput></screen>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-10-02 05:51:57 +01:00
|
|
|
<para>Unfortunately, there is no easy way to view the test results summary like
|
|
|
|
there was for the previous GCC package. However, if a failure occurs here, it
|
|
|
|
should be easy to spot. The output shown will contain something like:</para>
|
|
|
|
|
|
|
|
<blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote>
|
|
|
|
|
2003-08-09 12:45:03 +01:00
|
|
|
<para>And install the package:</para>
|
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>make install</userinput></screen>
|
2003-08-09 12:45:03 +01:00
|
|
|
|
2003-09-16 05:25:50 +01:00
|
|
|
<para>Now prepare Binutils for the re-adjusting of the toolchain in the next
|
|
|
|
chapter:</para>
|
2003-05-02 19:20:20 +01:00
|
|
|
|
2003-10-10 00:22:07 +01:00
|
|
|
<screen><userinput>make -C ld clean
|
|
|
|
make -C ld LIB_PATH=/usr/lib:/lib</userinput></screen>
|
2003-05-05 20:56:29 +01:00
|
|
|
|
2003-10-02 07:03:29 +01:00
|
|
|
<warning><para>Do not yet remove the Binutils source and build directories.
|
|
|
|
We'll need these directories again in the next chapter in the state they are in
|
|
|
|
now.</para></warning>
|
2003-05-02 19:20:20 +01:00
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|