gcc.xml 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
  3. <!ENTITY % general-entities SYSTEM "../general.ent">
  4. %general-entities;
  5. ]>
  6. <sect1 id="ch-system-gcc" xreflabel="GCC" role="wrap">
  7. <title>GCC-&gcc-version;</title>
  8. <?dbhtml filename="gcc.html"?>
  9. <indexterm zone="ch-system-gcc"><primary sortas="a-GCC">GCC</primary></indexterm>
  10. <sect2 role="package"><title/>
  11. <para>The GCC package contains the GNU compiler collection, which includes
  12. the C and C++ compilers.</para>
  13. <segmentedlist>
  14. <segtitle>&buildtime;</segtitle>
  15. <segtitle>&diskspace;</segtitle>
  16. <seglistitem><seg>11.7 SBU</seg><seg>294 MB</seg></seglistitem>
  17. </segmentedlist>
  18. <segmentedlist>
  19. <segtitle>GCC installation depends on</segtitle>
  20. <seglistitem><seg>Bash, Binutils, Coreutils, Diffutils, Findutils,
  21. Gawk, Gettext, Glibc, Grep, Make, Perl, Sed, Texinfo</seg></seglistitem>
  22. </segmentedlist>
  23. </sect2>
  24. <sect2 role="installation">
  25. <title>Installation of GCC</title>
  26. <para>This package is known to behave badly when you have changed its
  27. default optimization flags (including the -march and -mcpu options).
  28. Therefore, if you have defined any environment variables that override
  29. default optimizations, such as CFLAGS and CXXFLAGS, we recommend un-setting
  30. or modifying them when building GCC.</para>
  31. <para>Unpack the GCC-core <emphasis>and</emphasis> the GCC-g++ tarball -- they
  32. will unfold into the same directory. You should likewise extract the
  33. GCC-testsuite package. The full GCC package contains even more
  34. compilers. Instructions for building these can be found at
  35. <ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para>
  36. <para>First apply only the No-Fixincludes patch (and <emphasis>not</emphasis>
  37. the Specs patch) also used in the previous chapter:</para>
  38. <screen><userinput>patch -Np1 -i ../gcc-&gcc-version;-no-fixincludes-1.patch</userinput></screen>
  39. <para>Now apply a sed substitution that will suppress the installation of
  40. <filename>libiberty.a</filename>. We want to use the version of
  41. <filename>libiberty.a</filename> provided by Binutils:</para>
  42. <screen><userinput>sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in</userinput></screen>
  43. <para>The GCC documentation recommends building GCC outside of the source
  44. directory in a dedicated build directory:</para>
  45. <screen><userinput>mkdir ../gcc-build
  46. cd ../gcc-build</userinput></screen>
  47. <para>Now prepare GCC for compilation:</para>
  48. <screen><userinput>../gcc-&gcc-version;/configure --prefix=/usr \
  49. --libexecdir=/usr/lib --enable-shared --enable-threads=posix \
  50. --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++
  51. </userinput></screen>
  52. <para>Compile the package:</para>
  53. <screen><userinput>make</userinput></screen>
  54. <important><para>The test suite for GCC in this section is considered
  55. <emphasis>critical</emphasis>. Our advice is to not skip it under any
  56. circumstance.</para></important>
  57. <para>Test the results, but don't stop at errors (you'll remember the few
  58. known ones):</para>
  59. <screen><userinput>make -k check</userinput></screen>
  60. <para>The test suite notes from <xref linkend="ch-tools-gcc-pass2"/> are still very
  61. much appropriate here. Be sure to refer back there should you have any
  62. doubts.</para>
  63. <para>Now install the package:</para>
  64. <screen><userinput>make install</userinput></screen>
  65. <para>Some packages expect the C PreProcessor to be installed in the
  66. <filename>/lib</filename> directory.
  67. To support those packages, create this symlink:</para>
  68. <screen><userinput>ln -s ../usr/bin/cpp /lib</userinput></screen>
  69. <para>Many packages use the name <command>cc</command> to call the C
  70. compiler. To satisfy those packages, create a symlink:</para>
  71. <screen><userinput>ln -s gcc /usr/bin/cc</userinput></screen>
  72. <note><para>At this point it is strongly recommended to repeat the sanity check
  73. we performed earlier in this chapter. Refer back to
  74. <xref linkend="ch-system-readjusting"/> and repeat the check. If the results
  75. are wrong, then most likely you erroneously applied the GCC Specs patch from
  76. <xref linkend="chapter-temporary-tools"/>.</para></note>
  77. </sect2>
  78. <sect2 id="contents-gcc"><title>Contents of GCC</title>
  79. <para><emphasis>Installed programs</emphasis>: c++, cc (link to gcc),
  80. cc1, cc1plus, collect2, cpp, g++, gcc, gccbug, and gcov</para>
  81. <para><emphasis>Installed libraries</emphasis>: libgcc.a, libgcc_eh.a,
  82. libgcc_s.so, libstdc++.[a,so] and libsupc++.a</para>
  83. </sect2>
  84. <sect2><title>Short descriptions</title>
  85. <indexterm zone="ch-system-gcc cpp"><primary sortas="b-cpp">cpp</primary></indexterm>
  86. <para id="cpp"><command>cpp</command> is the C preprocessor. It is used by the
  87. compiler to have the #include and #define and such statements expanded in
  88. the source files.</para>
  89. <indexterm zone="ch-system-gcc g"><primary sortas="b-g++">g++</primary></indexterm>
  90. <para id="g"><command>g++</command> is the C++ compiler.</para>
  91. <indexterm zone="ch-system-gcc gcc"><primary sortas="b-gcc">gcc</primary></indexterm>
  92. <para id="gcc"><command>gcc</command> is the C compiler. It is used to translate
  93. the source code of a program into assembly code.</para>
  94. <indexterm zone="ch-system-gcc gccbug"><primary sortas="b-gccbug">gccbug</primary></indexterm>
  95. <para id="gccbug"><command>gccbug</command> is a shell script used to help create
  96. good bug reports.</para>
  97. <indexterm zone="ch-system-gcc gcov"><primary sortas="b-gcov">gcov</primary></indexterm>
  98. <para id="gcov"><command>gcov</command> is a coverage testing tool. It is used to
  99. analyze programs to find out where optimizations will have the most effect.</para>
  100. <indexterm zone="ch-system-gcc libgcc"><primary sortas="c-libgcc*">libgcc*</primary></indexterm>
  101. <para id="libgcc"><command>libgcc*</command> contains run-time support for gcc.</para>
  102. <indexterm zone="ch-system-gcc libstdc"><primary sortas="c-libstdc++">libstdc++</primary></indexterm>
  103. <para id="libstdc"><command>libstdc++</command> is the standard C++ library. It contains
  104. many frequently-used functions.</para>
  105. <indexterm zone="ch-system-gcc libsupc"><primary sortas="c-libsupc++">libsupc++</primary></indexterm>
  106. <para id="libsupc"><command>libsupc++</command> provides supporting routines
  107. for the c++ programming language.</para>
  108. </sect2>
  109. </sect1>