12345678910111213141516171819202122232425262728293031323334353637383940414243 |
- <sect2><title> </title><para> </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>Next, prepare Binutils to be compiled:</para>
- <para><screen><userinput>../binutils-&binutils-version;/configure \
- --prefix=/usr --enable-shared</userinput></screen></para>
- <para>Continue with compiling the package:</para>
- <para><screen><userinput>make tooldir=/usr</userinput></screen></para>
- <para><screen><userinput>make check</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, /usr/i686-pc-linux-gnu. Since we only build for our
- own system, we don't need this target specific directory in /usr. That
- setup would be used if the system was used to cross-compile (for example
- compiling a package on the Intel machine that generates code that can be
- executed on Apple PowerPC machines).</para>
- <para>Install the package:</para>
- <para><screen><userinput>make tooldir=/usr install</userinput></screen></para>
- <para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>
- </sect2>
|