[3be4d97] | 1 | <sect1 id="ch-tools-binutils-pass1">
|
---|
[bc82645e] | 2 | <title>Installing Binutils-&binutils-version; - Pass 1</title>
|
---|
| 3 | <?dbhtml filename="binutils-pass1.html" dir="chapter05"?>
|
---|
| 4 |
|
---|
[69276a94] | 5 | <screen>&buildtime; &binutils-time-tools-pass1;
|
---|
| 6 | &diskspace; &binutils-compsize-tools-pass1;</screen>
|
---|
[bc82645e] | 7 |
|
---|
[5888299] | 8 | &aa-binutils-down;
|
---|
[d0dfce4] | 9 | &aa-binutils-dep;
|
---|
[73aedd1d] | 10 |
|
---|
| 11 | <sect2><title> </title><para> </para></sect2>
|
---|
| 12 |
|
---|
| 13 | <sect2>
|
---|
| 14 | <title>Installation of Binutils</title>
|
---|
| 15 |
|
---|
| 16 | <para>It is important that Binutils be the first package to get compiled,
|
---|
| 17 | because both Glibc and GCC perform various tests on the available linker and
|
---|
| 18 | assembler to determine which of their own features to enable.</para>
|
---|
| 19 |
|
---|
| 20 | <para>This package is known to behave badly when you have changed its default
|
---|
| 21 | optimization flags (including the -march and -mcpu options). Therefore, if
|
---|
| 22 | you have defined any environment variables that override default
|
---|
| 23 | optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or
|
---|
| 24 | modifying them when building Binutils.</para>
|
---|
| 25 |
|
---|
| 26 | <para>The Binutils documentation recommends building Binutils outside of the
|
---|
| 27 | source directory in a dedicated build directory:</para>
|
---|
| 28 |
|
---|
| 29 | <screen><userinput>mkdir ../binutils-build
|
---|
| 30 | cd ../binutils-build</userinput></screen>
|
---|
| 31 |
|
---|
| 32 | <note><para>If you want the SBU values listed in the rest of the book to be of
|
---|
| 33 | any use, you will have to measure the time it takes to build this package. To
|
---|
| 34 | achieve this easily, you could do something like:
|
---|
| 35 | <userinput>time { ./configure ... && ... && ... && make install; }</userinput>.</para></note>
|
---|
| 36 |
|
---|
| 37 | <para>Now prepare Binutils for compilation:</para>
|
---|
| 38 |
|
---|
[c288d97] | 39 | <screen><userinput>../&binutils-dir;/configure --prefix=/tools --disable-nls</userinput></screen>
|
---|
[73aedd1d] | 40 |
|
---|
| 41 | <para>The meaning of the configure options:</para>
|
---|
| 42 |
|
---|
| 43 | <itemizedlist>
|
---|
| 44 | <listitem><para><userinput>--prefix=/tools</userinput>: This tells the
|
---|
| 45 | configure script to prepare to install the Binutils programs in the
|
---|
| 46 | <filename>/tools</filename> directory.</para></listitem>
|
---|
| 47 |
|
---|
| 48 | <listitem><para><userinput>--disable-nls</userinput>: This disables
|
---|
| 49 | internationalization (a word often shortened to i18n). We don't need this
|
---|
| 50 | for our static programs and <emphasis>nls</emphasis> often causes problems
|
---|
| 51 | when linking statically.</para></listitem>
|
---|
| 52 | </itemizedlist>
|
---|
| 53 |
|
---|
| 54 | <para>Continue with compiling the package:</para>
|
---|
| 55 |
|
---|
| 56 | <screen><userinput>make configure-host
|
---|
| 57 | make LDFLAGS="-all-static"</userinput></screen>
|
---|
| 58 |
|
---|
[5763f675] | 59 | <para>The meaning of the make parameters:</para>
|
---|
[73aedd1d] | 60 |
|
---|
| 61 | <itemizedlist>
|
---|
| 62 | <listitem><para><userinput>configure-host</userinput>: This forces all the
|
---|
| 63 | subdirectories to be configured immediately. A statically linked build will
|
---|
| 64 | fail without it. We therefore use this option to work around the
|
---|
| 65 | problem.</para></listitem>
|
---|
| 66 |
|
---|
| 67 | <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the
|
---|
| 68 | linker that all the Binutils programs should be linked statically. However,
|
---|
[90e3cb3] | 69 | strictly speaking, <emphasis>"-all-static"</emphasis> is first passed to the
|
---|
| 70 | <command>libtool</command> program which then passes
|
---|
| 71 | <emphasis>"-static"</emphasis> on to the linker.</para></listitem>
|
---|
[73aedd1d] | 72 | </itemizedlist>
|
---|
| 73 |
|
---|
[443cace] | 74 | <para>Compilation is now complete. This is the point where we would normally
|
---|
| 75 | run the test suite. But as discussed earlier, we don't recommend running the
|
---|
| 76 | test suites for the temporary tools here in this chapter. However, even if we
|
---|
| 77 | still wanted to run the Binutils test suite, we're unable do so at this early
|
---|
| 78 | stage because the test suite framework is not yet in place. Not only that, the
|
---|
| 79 | programs from this first pass will soon be overwritten by those installed in
|
---|
| 80 | the second pass.</para>
|
---|
| 81 |
|
---|
[73aedd1d] | 82 | <para>And install the package:</para>
|
---|
| 83 |
|
---|
| 84 | <screen><userinput>make install</userinput></screen>
|
---|
| 85 |
|
---|
| 86 | <para>Now prepare the linker for the "locking in" of Glibc later on:</para>
|
---|
| 87 |
|
---|
| 88 | <screen><userinput>make -C ld clean
|
---|
| 89 | make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen>
|
---|
| 90 |
|
---|
[5763f675] | 91 | <para>The meaning of the make parameters:</para>
|
---|
[73aedd1d] | 92 |
|
---|
| 93 | <itemizedlist>
|
---|
| 94 | <listitem><para><userinput>-C ld clean</userinput>: This tells the make program
|
---|
| 95 | to remove all the compiled files, but only in the <filename>ld</filename>
|
---|
| 96 | subdirectory.</para></listitem>
|
---|
| 97 |
|
---|
| 98 | <listitem><para><userinput>-C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput>:
|
---|
| 99 | This option rebuilds everything in the <filename>ld</filename> subdirectory.
|
---|
| 100 | Specifying the LIB_PATH makefile variable on the command line allows us to
|
---|
| 101 | override the default value and have it point to our temporary tools location.
|
---|
| 102 | The value of this variable specifies the linker's default library search path.
|
---|
| 103 | You'll see how this preparation is used later on in the
|
---|
| 104 | chapter.</para></listitem>
|
---|
| 105 | </itemizedlist>
|
---|
| 106 |
|
---|
| 107 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
| 108 | <literallayout></literallayout>
|
---|
| 109 |
|
---|
| 110 | <warning><para>Do not yet remove the Binutils build and source directories. You
|
---|
| 111 | will need them again in their current state a bit further on in this
|
---|
| 112 | chapter.</para></warning>
|
---|
| 113 |
|
---|
| 114 | <!-- HACK - Force some whitespace to appease tidy -->
|
---|
| 115 | <literallayout></literallayout>
|
---|
| 116 |
|
---|
| 117 | </sect2>
|
---|
[bc82645e] | 118 |
|
---|
[5888299] | 119 | <sect2><title> </title><para> </para>
|
---|
| 120 | <para>The details on this package are found in <xref linkend="contents-binutils"/>.</para>
|
---|
| 121 | <para> </para></sect2>
|
---|
| 122 |
|
---|
[bc82645e] | 123 | </sect1>
|
---|
| 124 |
|
---|