gcc-inst.xml 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. <sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
  2. <sect2>
  3. <title>Installation of GCC</title>
  4. <note><para>The test suite for GCC in this section is considered <emphasis>
  5. critical</emphasis>. Do not skip it under any circumstances.</para></note>
  6. <para>This package is known to behave badly when you have changed its
  7. default optimization flags (including the -march and -mcpu options).
  8. Therefore, if you have defined any environment variables that override
  9. default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
  10. or modifying them when building GCC.</para>
  11. <para>This time we will build both the C and the C++ compiler, so you'll have
  12. to unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
  13. will unfold into the same directory. You should likewise extract the
  14. GCC-testsuite package. The full GCC package contains even more
  15. compilers. Instructions for building these can be found at
  16. <ulink url="&blfs-root;view/cvs/general/gcc.html"/>.</para>
  17. <para><screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-2.patch
  18. patch -Np1 -i ../gcc-3.3.1-suppress-libiberty.patch</userinput></screen></para>
  19. <para>The second patch here suppresses the installation of libiberty from GCC,
  20. as we will use the one provided by binutils instead.</para>
  21. <para>The GCC documentation recommends building GCC outside of the source
  22. directory in a dedicated build directory:</para>
  23. <para><screen><userinput>mkdir ../gcc-build
  24. cd ../gcc-build</userinput></screen></para>
  25. <para>Now prepare GCC for compilation:</para>
  26. <para><screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
  27. &nbsp;&nbsp;&nbsp;&nbsp;--enable-shared --enable-threads=posix \
  28. &nbsp;&nbsp;&nbsp;&nbsp;--enable-__cxa_atexit --enable-clocale=gnu \
  29. &nbsp;&nbsp;&nbsp;&nbsp;--enable-languages=c,c++</userinput></screen></para>
  30. <para>Compile the package:</para>
  31. <para><screen><userinput>make</userinput></screen></para>
  32. <para>Test the results, but don't stop at errors (you'll remember the few
  33. known ones):</para>
  34. <para><screen><userinput>make -k check</userinput></screen></para>
  35. <para>And install the package:</para>
  36. <para><screen><userinput>make install</userinput></screen></para>
  37. <para>Some packages expect the C PreProcessor to be installed in the
  38. <filename>/lib</filename> directory.
  39. To honor those packages, create this symlink:</para>
  40. <para><screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen></para>
  41. <para>Many packages use the name <userinput>cc</userinput> to call the C
  42. compiler. To satisfy those packages, create a symlink:</para>
  43. <para><screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen></para>
  44. </sect2>