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 test suite at this early stage. First, the test suite 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>The Binutils documentation recommends building Binutils outside of the
|
---|
22 | source directory in a dedicated build 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 options:</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 |
|
---|
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>
|
---|
43 | </itemizedlist>
|
---|
44 |
|
---|
45 | <para>Continue with compiling the package:</para>
|
---|
46 |
|
---|
47 | <para><screen><userinput>make configure-host
|
---|
48 | make LDFLAGS="-all-static"</userinput></screen></para>
|
---|
49 |
|
---|
50 | <para>The meaning of the make option:</para>
|
---|
51 |
|
---|
52 | <itemizedlist>
|
---|
53 | <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the
|
---|
54 | linker that all the Binutils programs should be linked statically. However,
|
---|
55 | strictly speaking, <userinput>"-all-static"</userinput> is first passed to the
|
---|
56 | <emphasis>libtool</emphasis> program which then passes
|
---|
57 | <userinput>"-static"</userinput> on to the linker.</para></listitem>
|
---|
58 | </itemizedlist>
|
---|
59 |
|
---|
60 | <para>And install the package:</para>
|
---|
61 |
|
---|
62 | <para><screen><userinput>make install</userinput></screen></para>
|
---|
63 |
|
---|
64 | <para>Now prepare the linker for the "locking in" of Glibc later on:</para>
|
---|
65 |
|
---|
66 | <para><screen><userinput>make -C ld clean
|
---|
67 | make -C ld LIB_PATH=/tools/lib</userinput></screen></para>
|
---|
68 |
|
---|
69 | <para>The meaning of the make options:</para>
|
---|
70 |
|
---|
71 | <itemizedlist>
|
---|
72 | <listitem><para><userinput>-C ld clean</userinput>: This tells the make program
|
---|
73 | to remove all the compiled files, but only in the <filename>ld</filename>
|
---|
74 | subdirectory.</para></listitem>
|
---|
75 |
|
---|
76 | <listitem><para><userinput>-C ld LIB_PATH=/tools/lib</userinput>: This option
|
---|
77 | rebuilds everything in the <filename>ld</filename> subdirectory. Specifying the
|
---|
78 | LIB_PATH makefile variable on the command line allows us to override the default
|
---|
79 | value and have it point to our temporary tools location. The value of this
|
---|
80 | variable specifies the linker's default library search path. You'll see how this
|
---|
81 | preparation is utilised later on in the chapter.</para></listitem>
|
---|
82 | </itemizedlist>
|
---|
83 |
|
---|
84 | <caution><para>Do not yet remove the Binutils build and source
|
---|
85 | directories. You will need them again in their current state a bit further on
|
---|
86 | in this chapter.</para></caution>
|
---|
87 |
|
---|
88 | </sect2>
|
---|
89 |
|
---|