[ce14c07] | 1 | <sect2><title> </title><para> </para></sect2>
|
---|
| 2 |
|
---|
[6370fa6] | 3 | <sect2>
|
---|
| 4 | <title>Installation of Binutils</title>
|
---|
| 5 |
|
---|
[66e4325] | 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 |
|
---|
[1f53626] | 10 | <note><para>Even though Binutils is an important toolchain package, we are not
|
---|
[39dbad2] | 11 | going to run the test suite at this early stage. First, the test suite framework
|
---|
[40f4d66] | 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>
|
---|
[1f53626] | 14 |
|
---|
[28360cb] | 15 | <para>This package is known to behave badly when you have changed its default
|
---|
[2b114b25] | 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
|
---|
[66e4325] | 19 | modifying them when building Binutils.</para>
|
---|
[b43aab1] | 20 |
|
---|
[677aef3] | 21 | <para>The Binutils documentation recommends building Binutils outside of the
|
---|
| 22 | source directory in a dedicated build directory:</para>
|
---|
[6370fa6] | 23 |
|
---|
[21ba4e3] | 24 | <screen><userinput>mkdir ../binutils-build
|
---|
| 25 | cd ../binutils-build</userinput></screen>
|
---|
[d6bc819] | 26 |
|
---|
[1bbb24b] | 27 | <para>Next, prepare Binutils to be compiled:</para>
|
---|
| 28 |
|
---|
[21ba4e3] | 29 | <screen><userinput>../binutils-&binutils-version;/configure \
|
---|
| 30 | --prefix=/tools --disable-nls</userinput></screen>
|
---|
[1bbb24b] | 31 |
|
---|
[aa49729] | 32 | <para>The meaning of the configure options:</para>
|
---|
[1bbb24b] | 33 |
|
---|
| 34 | <itemizedlist>
|
---|
[148bb04] | 35 | <listitem><para><userinput>--prefix=/tools</userinput>: This tells the
|
---|
[66e4325] | 36 | configure script to prepare to install the Binutils programs in the
|
---|
[148bb04] | 37 | <filename>/tools</filename> directory.</para></listitem>
|
---|
[3a788f0c] | 38 |
|
---|
[66e4325] | 39 | <listitem><para><userinput>--disable-nls</userinput>: This disables
|
---|
| 40 | internationalization (a word often shortened to i18n). We don't need this
|
---|
| 41 | for our static programs and <emphasis>nls</emphasis> often causes problems
|
---|
| 42 | when linking statically.</para></listitem>
|
---|
[1bbb24b] | 43 | </itemizedlist>
|
---|
| 44 |
|
---|
[4a88065] | 45 | <para>Continue with compiling the package:</para>
|
---|
[1bbb24b] | 46 |
|
---|
[21ba4e3] | 47 | <screen><userinput>make configure-host
|
---|
| 48 | make LDFLAGS="-all-static"</userinput></screen>
|
---|
[6370fa6] | 49 |
|
---|
[3301fb6] | 50 | <para>The meaning of the make options:</para>
|
---|
[90423c0] | 51 |
|
---|
| 52 | <itemizedlist>
|
---|
[3301fb6] | 53 | <listitem><para><userinput>configure-host</userinput>: This forces all the
|
---|
| 54 | subdirectories to be configured immediately. A statically linked build will
|
---|
[a08cb59] | 55 | fail without it. We therefore use this option to work around the
|
---|
[3301fb6] | 56 | problem.</para></listitem>
|
---|
| 57 |
|
---|
[aa49729] | 58 | <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the
|
---|
| 59 | linker that all the Binutils programs should be linked statically. However,
|
---|
[dcca029] | 60 | strictly speaking, <userinput>"-all-static"</userinput> is first passed to the
|
---|
| 61 | <emphasis>libtool</emphasis> program which then passes
|
---|
[aa49729] | 62 | <userinput>"-static"</userinput> on to the linker.</para></listitem>
|
---|
[90423c0] | 63 | </itemizedlist>
|
---|
[1bbb24b] | 64 |
|
---|
[66e4325] | 65 | <para>And install the package:</para>
|
---|
[4a88065] | 66 |
|
---|
[21ba4e3] | 67 | <screen><userinput>make install</userinput></screen>
|
---|
[4a88065] | 68 |
|
---|
[18b65e2b] | 69 | <para>Now prepare the linker for the "locking in" of Glibc later on:</para>
|
---|
[66e4325] | 70 |
|
---|
[21ba4e3] | 71 | <screen><userinput>make -C ld clean
|
---|
| 72 | make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen>
|
---|
[bc82645e] | 73 |
|
---|
[aa49729] | 74 | <para>The meaning of the make options:</para>
|
---|
| 75 |
|
---|
| 76 | <itemizedlist>
|
---|
| 77 | <listitem><para><userinput>-C ld clean</userinput>: This tells the make program
|
---|
[3a788f0c] | 78 | to remove all the compiled files, but only in the <filename>ld</filename>
|
---|
[aa49729] | 79 | subdirectory.</para></listitem>
|
---|
| 80 |
|
---|
[1e66abe] | 81 | <listitem><para><userinput>-C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput>:
|
---|
| 82 | This option rebuilds everything in the <filename>ld</filename> subdirectory.
|
---|
| 83 | Specifying the LIB_PATH makefile variable on the command line allows us to
|
---|
| 84 | override the default value and have it point to our temporary tools location.
|
---|
| 85 | The value of this variable specifies the linker's default library search path.
|
---|
[076ddfe] | 86 | You'll see how this preparation is used later on in the
|
---|
[1e66abe] | 87 | chapter.</para></listitem>
|
---|
[aa49729] | 88 | </itemizedlist>
|
---|
| 89 |
|
---|
[e3a72b1] | 90 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
| 91 | <literallayout></literallayout>
|
---|
| 92 |
|
---|
[e4df1fc] | 93 | <warning><para>Do not yet remove the Binutils build and source directories. You
|
---|
| 94 | will need them again in their current state a bit further on in this
|
---|
| 95 | chapter.</para></warning>
|
---|
[bc82645e] | 96 |
|
---|
[e3a72b1] | 97 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
| 98 | <literallayout></literallayout>
|
---|
| 99 |
|
---|
[6370fa6] | 100 | </sect2>
|
---|
| 101 |
|
---|