source: chapter05/binutils-pass1-inst.xml@ 255504f

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 255504f was 677aef3, checked in by Greg Schafer <greg@…>, 21 years ago

GCC 2.95.3 fixes and other misc. toolchain related textual adjustments.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2861 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.7 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</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,
7because both Glibc and GCC perform various tests on the available linker and
8assembler 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
11going to run the test suite at this early stage. First, the test suite framework
12is not yet in place and second, the programs from this first pass will soon be
13overwritten 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
16optimization flags (including the -march and -mcpu options). Therefore, if
17you have defined any environment variables that override default
18optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or
19modifying them when building Binutils.</para>
20
21<para>The Binutils documentation recommends building Binutils outside of the
22source directory in a dedicated build directory:</para>
23
24<para><screen><userinput>mkdir ../binutils-build
25cd ../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&nbsp;&nbsp;&nbsp;&nbsp;--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
36configure 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
39internationalization (a word often shortened to i18n). We don't need this
40for our static programs and <emphasis>nls</emphasis> often causes problems
41when linking statically.</para></listitem>
42</itemizedlist>
43
44<para>Continue with compiling the package:</para>
45
46<para><screen><userinput>make configure-host
47make 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
53the linker that all the Binutils programs should be linked
54statically.</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
64make -C ld LIB_PATH=/tools/lib</userinput></screen></para>
65
66<caution><para>Do not yet remove the Binutils build and source
67directories. You will need them again in their current state a bit further on
68in this chapter.</para></caution>
69
70</sect2>
71
Note: See TracBrowser for help on using the repository browser.