binutils-inst.xml 1.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. <sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
  2. <sect2><title>Installation of Binutils</title>
  3. <para>This package is known to behave badly when you have changed its
  4. default optimization flags (including the -march and -mcpu options).
  5. Therefore, if you have defined any environment variables that override
  6. default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
  7. or modifying them when building binutils.</para>
  8. <para>It is recommended by the Binutils installation documentation to build
  9. Binutils outside of the source directory:</para>
  10. <para><screen><userinput>mkdir ../binutils-build
  11. cd ../binutils-build</userinput></screen></para>
  12. <para>Next, prepare Binutils to be compiled:</para>
  13. <para><screen><userinput>../binutils-&binutils-version;/configure \
  14. &nbsp;&nbsp;&nbsp;&nbsp;--prefix=/usr --enable-shared</userinput></screen></para>
  15. <para>Continue with compiling the package:</para>
  16. <para><screen><userinput>make tooldir=/usr</userinput></screen></para>
  17. <para><screen><userinput>make check</userinput></screen></para>
  18. <para>Normally, the <emphasis>tooldir</emphasis> (the directory where the
  19. executables end up) is set to $(exec_prefix)/$(target_alias) which expands
  20. into, for example, /usr/i686-pc-linux-gnu. Since we only build for our
  21. own system, we don't need this target specific directory in /usr. That
  22. setup would be used if the system was used to cross-compile (for example
  23. compiling a package on the Intel machine that generates code that can be
  24. executed on Apple PowerPC machines).</para>
  25. <para>Install the package:</para>
  26. <para><screen><userinput>make tooldir=/usr install</userinput></screen></para>
  27. <para><screen><userinput>rm /usr/lib/libiberty.a</userinput></screen></para>
  28. </sect2>