source: chapter05/binutils-inst.xml@ f8a5e31d

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 v4_1 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 f8a5e31d was 4a88065, checked in by Gerard Beekmans <gerard@…>, 21 years ago

reworded for consistency

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

  • Property mode set to 100644
File size: 2.0 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
3<sect2>
4<title>Installation of Binutils</title>
5
6<para>This package is known to behave badly when you have changed its default
7optimization flags (including the -march and -mcpu options). Binutils is
8best left alone. Therefore, if you have defined any environment variables
9that override default optimizations, such as CFLAGS and CXXFLAGS, we
10recommend unsetting or modifying them when building binutils. You have been
11warned.</para>
12
13<para>It is recommended by the Binutils installation documentation to build
14Binutils outside of the source directory in a dedicated directory:</para>
15
16<para><screen><userinput>mkdir ../binutils-build
17cd ../binutils-build</userinput></screen></para>
18
19<para>Next, prepare Binutils to be compiled:</para>
20
21<para><screen><userinput>../binutils-&binutils-version;/configure --prefix=$LFS/static --disable-nls</userinput></screen></para>
22
23<para>The meaning of the (new) configure switches are:</para>
24
25<itemizedlist>
26<listitem><para><userinput>--disable-nls:</userinput> This option disables
27internationalization (also known as i18n). We don't need this for our
28static programs and nls often causes problems when you're linking
29statically.</para></listitem>
30</itemizedlist>
31
32<para>Continue with compiling the package:</para>
33
34<para><screen><userinput>make LDFLAGS="-all-static"</userinput></screen></para>
35
36<para>The meaning of the make option is:</para>
37
38<itemizedlist>
39<listitem><para><userinput>make LDFLAGS="-all-static":</userinput> This is
40how we tell Binutils that all programs should be statically linked. Setting
41the <emphasis>LDFLAGS</emphasis> variable is the common way of specifying we
42want a static link to take place, however, its value and the way it is set
43is not always the same. You'll see with the remaining packages that there
44are different ways of setting up the <emphasis>LDFLAGS</emphasis>
45variable.</para></listitem>
46</itemizedlist>
47
48<para>And finish off installing the package:</para>
49
50<para><screen><userinput>make install</userinput></screen></para>
51
52</sect2>
53
Note: See TracBrowser for help on using the repository browser.