| 1 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 2 |
|
|---|
| 3 | <sect2>
|
|---|
| 4 | <title>Installation of Binutils</title>
|
|---|
| 5 |
|
|---|
| 6 | <para>It is important that Binutils be the first package to get compiled,
|
|---|
| 7 | because both Glibc and GCC perform various tests on the available linker and
|
|---|
| 8 | assembler to determine which of their own features to enable.</para>
|
|---|
| 9 |
|
|---|
| 10 | <note><para>Even though Binutils is an important toolchain package, we are not
|
|---|
| 11 | going to run the testsuite at this early stage. First, the testsuite framework
|
|---|
| 12 | is not yet in place and second, the programs from this first pass will soon be
|
|---|
| 13 | overwritten by those installed in the second pass.</para></note>
|
|---|
| 14 |
|
|---|
| 15 | <para>This package is known to behave badly when you have changed its default
|
|---|
| 16 | optimization flags (including the -march and -mcpu options). Therefore, if
|
|---|
| 17 | you have defined any environment variables that override default
|
|---|
| 18 | optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or
|
|---|
| 19 | modifying them when building Binutils.</para>
|
|---|
| 20 |
|
|---|
| 21 | <para>It is recommended by the Binutils installation documentation to build
|
|---|
| 22 | Binutils outside of the source directory in a dedicated directory:</para>
|
|---|
| 23 |
|
|---|
| 24 | <para><screen><userinput>mkdir ../binutils-build
|
|---|
| 25 | cd ../binutils-build</userinput></screen></para>
|
|---|
| 26 |
|
|---|
| 27 | <para>Next, prepare Binutils to be compiled:</para>
|
|---|
| 28 |
|
|---|
| 29 | <para><screen><userinput>../binutils-&binutils-version;/configure \
|
|---|
| 30 | --prefix=/tools --disable-nls</userinput></screen></para>
|
|---|
| 31 |
|
|---|
| 32 | <para>The meaning of the configure switches:</para>
|
|---|
| 33 |
|
|---|
| 34 | <itemizedlist>
|
|---|
| 35 | <listitem><para><userinput>--prefix=/tools</userinput>: This tells the
|
|---|
| 36 | configure script to prepare to install the Binutils programs in the
|
|---|
| 37 | <filename>/tools</filename> directory.</para></listitem>
|
|---|
| 38 | <listitem><para><userinput>--disable-nls</userinput>: This disables
|
|---|
| 39 | internationalization (a word often shortened to i18n). We don't need this
|
|---|
| 40 | for our static programs and <emphasis>nls</emphasis> often causes problems
|
|---|
| 41 | when linking statically.</para></listitem>
|
|---|
| 42 | </itemizedlist>
|
|---|
| 43 |
|
|---|
| 44 | <para>Continue with compiling the package:</para>
|
|---|
| 45 |
|
|---|
| 46 | <para><screen><userinput>make configure-host
|
|---|
| 47 | make LDFLAGS="-all-static"</userinput></screen></para>
|
|---|
| 48 |
|
|---|
| 49 | <para>The meaning of the make option:</para>
|
|---|
| 50 |
|
|---|
| 51 | <itemizedlist>
|
|---|
| 52 | <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells
|
|---|
| 53 | the linker that all the Binutils programs should be linked
|
|---|
| 54 | statically.</para></listitem>
|
|---|
| 55 | </itemizedlist>
|
|---|
| 56 |
|
|---|
| 57 | <para>And install the package:</para>
|
|---|
| 58 |
|
|---|
| 59 | <para><screen><userinput>make install</userinput></screen></para>
|
|---|
| 60 |
|
|---|
| 61 | <para>Now prepare the linker for the "locking in" of Glibc later on:</para>
|
|---|
| 62 |
|
|---|
| 63 | <para><screen><userinput>make -C ld clean
|
|---|
| 64 | make -C ld LIB_PATH=/tools/lib</userinput></screen></para>
|
|---|
| 65 |
|
|---|
| 66 | <caution><para>Do not yet remove the Binutils build and source
|
|---|
| 67 | directories. You will need them again in their current state a bit further on
|
|---|
| 68 | in this chapter.</para></caution>
|
|---|
| 69 |
|
|---|
| 70 | </sect2>
|
|---|
| 71 |
|
|---|
