lfs/chapter06/binutils-inst.xml

<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>

<sect2><title>Installation of Binutils</title>

<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override
default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
or modifying them when building Binutils.</para>

<para>It is recommended by the Binutils installation documentation to build
Binutils outside of the source directory:</para>

<para><screen><userinput>mkdir ../binutils-build
cd ../binutils-build</userinput></screen></para>

<para>Now prepare Binutils for compilation:</para>

<para><screen><userinput>../binutils-&binutils-version;/configure \
&nbsp;&nbsp;&nbsp;&nbsp;--prefix=/usr --enable-shared</userinput></screen></para>

<para>Compile the package:</para>

<para><screen><userinput>make tooldir=/usr</userinput></screen></para>

<para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
executables end up) is set to $(exec_prefix)/$(target_alias), which expands
into, for example, <filename>/usr/i686-pc-linux-gnu</filename>. Since we only
build for our own system, we don't need this target specific directory in
<filename>/usr</filename>. That setup would be used if the system was used to
cross-compile (for example compiling a package on an Intel machine that
generates code that can be executed on PowerPC machines).</para>

<para>Check the results:</para>

<para><screen><userinput>make check</userinput></screen></para>

<para>Install the package:</para>

<para><screen><userinput>make tooldir=/usr install</userinput></screen></para>

<para>And remove a library that normally is not meant to be installed on its
own:</para>

<para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>

</sect2>