source: chapter06/binutils-inst.xml@ 2b114b25

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 2b114b25 was 2b114b25, checked in by Gerard Beekmans <gerard@…>, 21 years ago

textual changes

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

  • Property mode set to 100644
File size: 1.9 KB
Line 
1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
3<sect2><title>Installation of Binutils</title>
4
5<para>This package is known to behave badly when you have changed its
6default optimization flags (including the -march and -mcpu options).
7Therefore, if you have defined any environment variables that override
8default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
9or modifying them when building binutils.</para>
10
11<para>It is recommended by the Binutils installation documentation to build
12Binutils outside of the source directory:</para>
13
14<para><screen><userinput>mkdir ../binutils-build &amp;&amp;
15cd ../binutils-build</userinput></screen></para>
16
17<para>Next, prepare Binutils to be compiled:</para>
18
19<para><screen><userinput>../binutils-&binutils-version;/configure --prefix=/usr --enable-shared</userinput></screen></para>
20
21<para>Continue with compiling the package:</para>
22
23<para><screen><userinput>make tooldir=/usr</userinput></screen></para>
24
25<para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
26executables end up) is set to $(exec_prefix)/$(target_alias) which expands
27into, for example, /usr/i686-pc-linux-gnu. Since we only build for our
28own system, we don't need this target specific directory in /usr. That
29setup would be used if the system was used to cross-compile (for example
30compiling a package on the Intel machine that generates code that can be
31executed on Apple PowerPC machines).</para>
32
33<para>Install the package:</para>
34
35<para><screen><userinput>make tooldir=/usr install</userinput></screen></para>
36
37<para>Install the info pages:</para>
38
39<para><screen><userinput>make tooldir=/usr install-info</userinput></screen></para>
40
41<para>Some packages require the <emphasis>libiberty</emphasis> header
42in order to build. To honor those packages, install the file:</para>
43
44<para><screen><userinput>cp ../binutils-&binutils-version;/include/libiberty.h /usr/include</userinput></screen></para>
45
46</sect2>
47
Note: See TracBrowser for help on using the repository browser.