| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="ch-system-gcc" role="wrap">
|
|---|
| 9 | <?dbhtml filename="gcc.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <sect1info condition="script">
|
|---|
| 12 | <productname>gcc</productname>
|
|---|
| 13 | <productnumber>&gcc-version;</productnumber>
|
|---|
| 14 | <address>&gcc-url;</address>
|
|---|
| 15 | </sect1info>
|
|---|
| 16 |
|
|---|
| 17 | <title>GCC-&gcc-version;</title>
|
|---|
| 18 |
|
|---|
| 19 | <indexterm zone="ch-system-gcc">
|
|---|
| 20 | <primary sortas="a-GCC">GCC</primary>
|
|---|
| 21 | </indexterm>
|
|---|
| 22 |
|
|---|
| 23 | <sect2 role="package">
|
|---|
| 24 | <title/>
|
|---|
| 25 |
|
|---|
| 26 | <para>The GCC package contains the GNU compiler collection, which includes
|
|---|
| 27 | the C and C++ compilers.</para>
|
|---|
| 28 |
|
|---|
| 29 | <segmentedlist>
|
|---|
| 30 | <segtitle>&buildtime;</segtitle>
|
|---|
| 31 | <segtitle>&diskspace;</segtitle>
|
|---|
| 32 |
|
|---|
| 33 | <seglistitem>
|
|---|
| 34 | <seg>&gcc-fin-sbu;</seg>
|
|---|
| 35 | <seg>&gcc-fin-du;</seg>
|
|---|
| 36 | </seglistitem>
|
|---|
| 37 | </segmentedlist>
|
|---|
| 38 |
|
|---|
| 39 | </sect2>
|
|---|
| 40 |
|
|---|
| 41 | <sect2 role="installation">
|
|---|
| 42 | <title>Installation of GCC</title>
|
|---|
| 43 |
|
|---|
| 44 | <para>For x86_64 target, set the default directory name for
|
|---|
| 45 | 64-bit libraries to <filename class='directory'>lib</filename>. The
|
|---|
| 46 | command is unnecessary, but harmless for 32-bit x86. If you are
|
|---|
| 47 | building for another target, you may need to adjust the command for
|
|---|
| 48 | your target:</para>
|
|---|
| 49 |
|
|---|
| 50 | <screen><userinput remap="pre">sed -e '/m64=/s/lib64/lib/' \
|
|---|
| 51 | -i.orig gcc/config/i386/t-linux64</userinput></screen>
|
|---|
| 52 |
|
|---|
| 53 | <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>
|
|---|
| 54 |
|
|---|
| 55 | <screen><userinput remap="pre">mkdir -v build
|
|---|
| 56 | cd build</userinput></screen>
|
|---|
| 57 |
|
|---|
| 58 | <para>Prepare GCC for compilation:</para>
|
|---|
| 59 |
|
|---|
| 60 | <screen><userinput remap="configure">../configure --prefix=/usr \
|
|---|
| 61 | LD=ld \
|
|---|
| 62 | --enable-languages=c,c++ \
|
|---|
| 63 | --enable-default-pie \
|
|---|
| 64 | --enable-default-ssp \
|
|---|
| 65 | --enable-host-pie \
|
|---|
| 66 | --disable-multilib \
|
|---|
| 67 | --disable-bootstrap \
|
|---|
| 68 | --disable-fixincludes \
|
|---|
| 69 | --with-system-zlib</userinput></screen>
|
|---|
| 70 |
|
|---|
| 71 | <para>GCC supports seven different computer languages, but the
|
|---|
| 72 | prerequisites for most of them have not yet been installed. See the
|
|---|
| 73 | <ulink url="&blfs-book;general/gcc.html">BLFS Book GCC page</ulink>
|
|---|
| 74 | for instructions on how to build all of GCC's supported languages.</para>
|
|---|
| 75 |
|
|---|
| 76 | <variablelist>
|
|---|
| 77 | <title>The meaning of the new configure parameters:</title>
|
|---|
| 78 |
|
|---|
| 79 | <varlistentry>
|
|---|
| 80 | <term><parameter>LD=ld</parameter></term>
|
|---|
| 81 | <listitem>
|
|---|
| 82 | <para>This parameter makes the configure script use the ld program installed
|
|---|
| 83 | by the Binutils package built earlier in this chapter, rather than
|
|---|
| 84 | the cross-built version which would otherwise be used.</para>
|
|---|
| 85 | </listitem>
|
|---|
| 86 | </varlistentry>
|
|---|
| 87 |
|
|---|
| 88 | <varlistentry>
|
|---|
| 89 | <term><parameter>--disable-fixincludes</parameter></term>
|
|---|
| 90 | <listitem>
|
|---|
| 91 | <para>By default, during the installation of GCC some system
|
|---|
| 92 | headers would be <quote>fixed</quote> to be used with GCC. This
|
|---|
| 93 | is not necessary for a modern Linux system, and potentially
|
|---|
| 94 | harmful if a package is reinstalled after installing GCC. This
|
|---|
| 95 | switch prevents GCC from <quote>fixing</quote> the headers.</para>
|
|---|
| 96 | </listitem>
|
|---|
| 97 | </varlistentry>
|
|---|
| 98 |
|
|---|
| 99 | <varlistentry>
|
|---|
| 100 | <term><parameter>--with-system-zlib</parameter></term>
|
|---|
| 101 | <listitem>
|
|---|
| 102 | <para>This switch tells GCC to link to the system installed copy of
|
|---|
| 103 | the Zlib library, rather than its own internal copy.</para>
|
|---|
| 104 | </listitem>
|
|---|
| 105 | </varlistentry>
|
|---|
| 106 | </variablelist>
|
|---|
| 107 |
|
|---|
| 108 | <note>
|
|---|
| 109 | <anchor id="pie-ssp-info" xreflabel="note on PIE and SSP"/>
|
|---|
| 110 | <para>
|
|---|
| 111 | PIE (position-independent executables) are
|
|---|
| 112 | binary programs that can be loaded anywhere in memory. Without PIE,
|
|---|
| 113 | the security feature named ASLR (Address Space Layout Randomization)
|
|---|
| 114 | can be applied for the shared libraries, but not for the executables
|
|---|
| 115 | themselves. Enabling PIE allows ASLR for the executables in addition to
|
|---|
| 116 | the shared libraries, and mitigates some attacks based on fixed
|
|---|
| 117 | addresses of sensitive code or data in the executables.
|
|---|
| 118 | </para>
|
|---|
| 119 | <para>
|
|---|
| 120 | SSP (Stack Smashing Protection) is a technique to ensure
|
|---|
| 121 | that the parameter stack is not corrupted. Stack corruption can,
|
|---|
| 122 | for example, alter the return address of a subroutine,
|
|---|
| 123 | thus transferring control to some dangerous code
|
|---|
| 124 | (existing in the program or shared libraries, or injected by the
|
|---|
| 125 | attacker somehow).
|
|---|
| 126 | </para>
|
|---|
| 127 | </note>
|
|---|
| 128 |
|
|---|
| 129 | <para>Compile the package:</para>
|
|---|
| 130 |
|
|---|
| 131 | <screen><userinput remap="make">make</userinput></screen>
|
|---|
| 132 |
|
|---|
| 133 | <important>
|
|---|
| 134 | <para>In this section, the test suite for GCC is considered
|
|---|
| 135 | important, but it takes a long time. First-time builders are
|
|---|
| 136 | encouraged to run the test suite. The time to run the tests can be
|
|---|
| 137 | reduced significantly by adding -jx to the <command>make -k check</command>
|
|---|
| 138 | command below, where x is the number of CPU cores on your system.</para>
|
|---|
| 139 | </important>
|
|---|
| 140 |
|
|---|
| 141 | <para>One set of tests in the GCC test suite is known to exhaust the default
|
|---|
| 142 | stack, so increase the stack size prior to running the tests:</para>
|
|---|
| 143 |
|
|---|
| 144 | <screen><userinput remap="test">ulimit -s 32768</userinput></screen>
|
|---|
| 145 |
|
|---|
| 146 | <para>Now remove/fix several known test failures:</para>
|
|---|
| 147 |
|
|---|
| 148 | <screen><userinput remap="test">sed -e '/cpython/d' -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp
|
|---|
| 149 | sed -e 's/no-pic /&-no-pie /' -i ../gcc/testsuite/gcc.target/i386/pr113689-1.c
|
|---|
| 150 | sed -e 's/300000/(1|300000)/' -i ../libgomp/testsuite/libgomp.c-c++-common/pr109062.c
|
|---|
| 151 | sed -e 's/{ target nonpic } //' \
|
|---|
| 152 | -e '/GOTPCREL/d' -i ../gcc/testsuite/gcc.target/i386/fentryname3.c</userinput></screen>
|
|---|
| 153 |
|
|---|
| 154 | <para>Test the results as a non-privileged user, but do not stop at errors:</para>
|
|---|
| 155 |
|
|---|
| 156 | <screen><userinput remap="test">chown -R tester .
|
|---|
| 157 | su tester -c "PATH=$PATH make -k check"</userinput></screen>
|
|---|
| 158 |
|
|---|
| 159 | <para>To extract a summary of the test suite results, run:</para>
|
|---|
| 160 |
|
|---|
| 161 | <screen><userinput remap="test">../contrib/test_summary</userinput></screen>
|
|---|
| 162 |
|
|---|
| 163 | <para>To filter out only the summaries, pipe the output through
|
|---|
| 164 | <userinput>grep -A7 Summ</userinput>.</para>
|
|---|
| 165 |
|
|---|
| 166 | <para>Results can be compared with those located at <ulink
|
|---|
| 167 | url="&test-results;"/> and
|
|---|
| 168 | <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
|
|---|
| 169 | <!--
|
|---|
| 170 | <para>
|
|---|
| 171 | Eight gcc tests (out of over 185,000):
|
|---|
| 172 | <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename>
|
|---|
| 173 | and seven tests in the <filename class='directory'>analyzer</filename>
|
|---|
| 174 | directory are known to fail.
|
|---|
| 175 |
|
|---|
| 176 | <!- - https://gcc.gnu.org/PR109353 - ->
|
|---|
| 177 | One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is
|
|---|
| 178 | known to fail.
|
|---|
| 179 |
|
|---|
| 180 | For g++, 21 tests (out of approximately 250,000): 14
|
|---|
| 181 | <quote>AddressSanitizer*</quote>
|
|---|
| 182 | tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
|
|---|
| 183 | known to fail.
|
|---|
| 184 |
|
|---|
| 185 | Additionally, several tests in the
|
|---|
| 186 | <filename class='directory'>vect</filename> directory are known to fail
|
|---|
| 187 | if the hardware does not support AVX.</para>
|
|---|
| 188 | -->
|
|---|
| 189 | <para>A few unexpected failures cannot always be avoided. In some cases
|
|---|
| 190 | test failures depend on the specific hardware of the system.<!--The GCC developers
|
|---|
| 191 | are usually aware of these issues, but have not resolved them yet.-->
|
|---|
| 192 | Unless the test results are vastly different from those at the above URL,
|
|---|
| 193 | it is safe to continue.</para>
|
|---|
| 194 |
|
|---|
| 195 | <para>Install the package:</para>
|
|---|
| 196 |
|
|---|
| 197 | <screen><userinput remap="install">make install</userinput></screen>
|
|---|
| 198 |
|
|---|
| 199 | <para>The GCC build directory is owned by <systemitem class="username">
|
|---|
| 200 | tester</systemitem> now, and the ownership of the installed header
|
|---|
| 201 | directory (and its content) is incorrect. Change the ownership to the
|
|---|
| 202 | <systemitem class="username">root</systemitem> user and group:</para>
|
|---|
| 203 |
|
|---|
| 204 | <screen><userinput remap="install">chown -v -R root:root \
|
|---|
| 205 | /usr/lib/gcc/$(gcc -dumpmachine)/&gcc-version;/include{,-fixed}</userinput></screen>
|
|---|
| 206 |
|
|---|
| 207 | <para>Create a symlink required by the <ulink
|
|---|
| 208 | url="https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s09.html">FHS</ulink>
|
|---|
| 209 | for "historical" reasons.</para>
|
|---|
| 210 |
|
|---|
| 211 | <screen><userinput remap="install">ln -svr /usr/bin/cpp /usr/lib</userinput></screen>
|
|---|
| 212 |
|
|---|
| 213 | <para>Many packages use the name <command>cc</command> to call the C
|
|---|
| 214 | compiler. We've already created <command>cc</command> as a symlink in
|
|---|
| 215 | <xref linkend='ch-tools-gcc-pass2'/>, create its man page as a symlink
|
|---|
| 216 | as well:</para>
|
|---|
| 217 |
|
|---|
| 218 | <screen><userinput remap="install">ln -sv gcc.1 /usr/share/man/man1/cc.1</userinput></screen>
|
|---|
| 219 |
|
|---|
| 220 | <para>Add a compatibility symlink to enable building programs with
|
|---|
| 221 | Link Time Optimization (LTO):</para>
|
|---|
| 222 |
|
|---|
| 223 | <screen><userinput remap="install">ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \
|
|---|
| 224 | /usr/lib/bfd-plugins/</userinput></screen>
|
|---|
| 225 |
|
|---|
| 226 | <para>Now that our final toolchain is in place, it is important to again ensure
|
|---|
| 227 | that compiling and linking will work as expected. We do this by performing
|
|---|
| 228 | some sanity checks:</para>
|
|---|
| 229 |
|
|---|
| 230 | <screen><userinput>echo 'int main(){}' > dummy.c
|
|---|
| 231 | cc dummy.c -v -Wl,--verbose &> dummy.log
|
|---|
| 232 | readelf -l a.out | grep ': /lib'</userinput></screen>
|
|---|
| 233 |
|
|---|
| 234 | <para>There should be no errors,
|
|---|
| 235 | and the output of the last command will be (allowing for
|
|---|
| 236 | platform-specific differences in the dynamic linker name):</para>
|
|---|
| 237 |
|
|---|
| 238 | <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
|
|---|
| 239 |
|
|---|
| 240 | <para>Now make sure that we're set up to use the correct start files:</para>
|
|---|
| 241 |
|
|---|
| 242 | <screen><userinput>grep -E -o '/usr/lib.*/S?crt[1in].*succeeded' dummy.log</userinput></screen>
|
|---|
| 243 |
|
|---|
| 244 | <para>The output of the last command should be:</para>
|
|---|
| 245 |
|
|---|
| 246 | <screen><computeroutput>/usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/Scrt1.o succeeded
|
|---|
| 247 | /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded
|
|---|
| 248 | /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded</computeroutput></screen>
|
|---|
| 249 |
|
|---|
| 250 | <para>Depending on your machine architecture, the above may differ slightly.
|
|---|
| 251 | The difference will be the name of the directory
|
|---|
| 252 | after <filename class="directory">/usr/lib/gcc</filename>. The important
|
|---|
| 253 | thing to look for here is that <command>gcc</command> has found all three
|
|---|
| 254 | <filename>crt*.o</filename> files under the
|
|---|
| 255 | <filename class="directory">/usr/lib</filename> directory.</para>
|
|---|
| 256 |
|
|---|
| 257 | <para>Verify that the compiler is searching for the correct header
|
|---|
| 258 | files:</para>
|
|---|
| 259 |
|
|---|
| 260 | <screen><userinput>grep -B4 '^ /usr/include' dummy.log</userinput></screen>
|
|---|
| 261 |
|
|---|
| 262 | <para>This command should return the following output:</para>
|
|---|
| 263 |
|
|---|
| 264 | <screen><computeroutput>#include <...> search starts here:
|
|---|
| 265 | /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include
|
|---|
| 266 | /usr/local/include
|
|---|
| 267 | /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed
|
|---|
| 268 | /usr/include</computeroutput></screen>
|
|---|
| 269 |
|
|---|
| 270 | <para>Again, the directory named after your target triplet may be
|
|---|
| 271 | different than the above, depending on your system architecture.</para>
|
|---|
| 272 |
|
|---|
| 273 | <para>Next, verify that the new linker is being used with the correct search paths:</para>
|
|---|
| 274 |
|
|---|
| 275 | <screen><userinput>grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'</userinput></screen>
|
|---|
| 276 |
|
|---|
| 277 | <para>References to paths that have components with '-linux-gnu' should
|
|---|
| 278 | be ignored, but otherwise the output of the last command should be:</para>
|
|---|
| 279 |
|
|---|
| 280 | <screen><computeroutput>SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
|
|---|
| 281 | SEARCH_DIR("/usr/local/lib64")
|
|---|
| 282 | SEARCH_DIR("/lib64")
|
|---|
| 283 | SEARCH_DIR("/usr/lib64")
|
|---|
| 284 | SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
|
|---|
| 285 | SEARCH_DIR("/usr/local/lib")
|
|---|
| 286 | SEARCH_DIR("/lib")
|
|---|
| 287 | SEARCH_DIR("/usr/lib");</computeroutput></screen>
|
|---|
| 288 |
|
|---|
| 289 | <para>A 32-bit system may use a few other directories. For example, here
|
|---|
| 290 | is the output from an i686 machine:</para>
|
|---|
| 291 |
|
|---|
| 292 | <screen><computeroutput>SEARCH_DIR("/usr/i686-pc-linux-gnu/lib32")
|
|---|
| 293 | SEARCH_DIR("/usr/local/lib32")
|
|---|
| 294 | SEARCH_DIR("/lib32")
|
|---|
| 295 | SEARCH_DIR("/usr/lib32")
|
|---|
| 296 | SEARCH_DIR("/usr/i686-pc-linux-gnu/lib")
|
|---|
| 297 | SEARCH_DIR("/usr/local/lib")
|
|---|
| 298 | SEARCH_DIR("/lib")
|
|---|
| 299 | SEARCH_DIR("/usr/lib");</computeroutput></screen>
|
|---|
| 300 |
|
|---|
| 301 | <para>Next make sure that we're using the correct libc:</para>
|
|---|
| 302 |
|
|---|
| 303 | <screen><userinput>grep "/lib.*/libc.so.6 " dummy.log</userinput></screen>
|
|---|
| 304 |
|
|---|
| 305 | <para>The output of the last command should be:</para>
|
|---|
| 306 |
|
|---|
| 307 | <screen><computeroutput>attempt to open /usr/lib/libc.so.6 succeeded</computeroutput></screen>
|
|---|
| 308 |
|
|---|
| 309 | <para>Make sure GCC is using the correct dynamic linker:</para>
|
|---|
| 310 |
|
|---|
| 311 | <screen><userinput>grep found dummy.log</userinput></screen>
|
|---|
| 312 |
|
|---|
| 313 | <para>The output of the last command should be (allowing for
|
|---|
| 314 | platform-specific differences in dynamic linker name):</para>
|
|---|
| 315 |
|
|---|
| 316 | <screen><computeroutput>found ld-linux-x86-64.so.2 at /usr/lib/ld-linux-x86-64.so.2</computeroutput></screen>
|
|---|
| 317 |
|
|---|
| 318 | <para>If the output does not appear as shown above or is not received
|
|---|
| 319 | at all, then something is seriously wrong. Investigate and retrace the
|
|---|
| 320 | steps to find out where the problem is and correct it. <!--The most likely
|
|---|
| 321 | reason is that something went wrong with the specs file adjustment.--> Any
|
|---|
| 322 | issues should be resolved before continuing with the process.</para>
|
|---|
| 323 |
|
|---|
| 324 | <para>Once everything is working correctly, clean up the test files:</para>
|
|---|
| 325 |
|
|---|
| 326 | <screen><userinput>rm -v dummy.c a.out dummy.log</userinput></screen>
|
|---|
| 327 |
|
|---|
| 328 | <para>Finally, move a misplaced file:</para>
|
|---|
| 329 |
|
|---|
| 330 | <screen><userinput remap="install">mkdir -pv /usr/share/gdb/auto-load/usr/lib
|
|---|
| 331 | mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen>
|
|---|
| 332 |
|
|---|
| 333 | </sect2>
|
|---|
| 334 |
|
|---|
| 335 | <sect2 id="contents-gcc" role="content">
|
|---|
| 336 | <title>Contents of GCC</title>
|
|---|
| 337 |
|
|---|
| 338 | <segmentedlist>
|
|---|
| 339 | <segtitle>Installed programs</segtitle>
|
|---|
| 340 | <segtitle>Installed libraries</segtitle>
|
|---|
| 341 | <segtitle>Installed directories</segtitle>
|
|---|
| 342 |
|
|---|
| 343 | <seglistitem>
|
|---|
| 344 | <seg>c++, cc (link to gcc), cpp, g++, gcc,
|
|---|
| 345 | gcc-ar, gcc-nm, gcc-ranlib, gcov, gcov-dump, gcov-tool,
|
|---|
| 346 | and lto-dump</seg>
|
|---|
| 347 |
|
|---|
| 348 | <seg>libasan.{a,so}, libatomic.{a,so}, libcc1.so, libgcc.a, libgcc_eh.a,
|
|---|
| 349 | libgcc_s.so, libgcov.a, libgomp.{a,so}, libhwasan.{a,so}, libitm.{a,so},
|
|---|
| 350 | liblsan.{a,so}, liblto_plugin.so,
|
|---|
| 351 | libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a,
|
|---|
| 352 | libstdc++.{a,so}, libstdc++exp.a, libstdc++fs.a, libsupc++.a, libtsan.{a,so},
|
|---|
| 353 | and libubsan.{a,so}</seg>
|
|---|
| 354 |
|
|---|
| 355 | <seg>/usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, and
|
|---|
| 356 | /usr/share/gcc-&gcc-version;</seg>
|
|---|
| 357 | </seglistitem>
|
|---|
| 358 | </segmentedlist>
|
|---|
| 359 |
|
|---|
| 360 | <variablelist>
|
|---|
| 361 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
|---|
| 362 | <?dbfo list-presentation="list"?>
|
|---|
| 363 | <?dbhtml list-presentation="table"?>
|
|---|
| 364 |
|
|---|
| 365 | <varlistentry id="c">
|
|---|
| 366 | <term><command>c++</command></term>
|
|---|
| 367 | <listitem>
|
|---|
| 368 | <para>The C++ compiler</para>
|
|---|
| 369 | <indexterm zone="ch-system-gcc c">
|
|---|
| 370 | <primary sortas="b-c++">c++</primary>
|
|---|
| 371 | </indexterm>
|
|---|
| 372 | </listitem>
|
|---|
| 373 | </varlistentry>
|
|---|
| 374 |
|
|---|
| 375 | <varlistentry id="cc">
|
|---|
| 376 | <term><command>cc</command></term>
|
|---|
| 377 | <listitem>
|
|---|
| 378 | <para>The C compiler</para>
|
|---|
| 379 | <indexterm zone="ch-system-gcc cc">
|
|---|
| 380 | <primary sortas="b-cc">cc</primary>
|
|---|
| 381 | </indexterm>
|
|---|
| 382 | </listitem>
|
|---|
| 383 | </varlistentry>
|
|---|
| 384 |
|
|---|
| 385 | <varlistentry id="cpp">
|
|---|
| 386 | <term><command>cpp</command></term>
|
|---|
| 387 | <listitem>
|
|---|
| 388 | <para>The C preprocessor; it is used by the compiler to expand the
|
|---|
| 389 | #include, #define, and similar directives in the source files</para>
|
|---|
| 390 | <indexterm zone="ch-system-gcc cpp">
|
|---|
| 391 | <primary sortas="b-cpp">cpp</primary>
|
|---|
| 392 | </indexterm>
|
|---|
| 393 | </listitem>
|
|---|
| 394 | </varlistentry>
|
|---|
| 395 |
|
|---|
| 396 | <varlistentry id="g">
|
|---|
| 397 | <term><command>g++</command></term>
|
|---|
| 398 | <listitem>
|
|---|
| 399 | <para>The C++ compiler</para>
|
|---|
| 400 | <indexterm zone="ch-system-gcc g">
|
|---|
| 401 | <primary sortas="b-g++">g++</primary>
|
|---|
| 402 | </indexterm>
|
|---|
| 403 | </listitem>
|
|---|
| 404 | </varlistentry>
|
|---|
| 405 |
|
|---|
| 406 | <varlistentry id="gcc">
|
|---|
| 407 | <term><command>gcc</command></term>
|
|---|
| 408 | <listitem>
|
|---|
| 409 | <para>The C compiler</para>
|
|---|
| 410 | <indexterm zone="ch-system-gcc gcc">
|
|---|
| 411 | <primary sortas="b-gcc">gcc</primary>
|
|---|
| 412 | </indexterm>
|
|---|
| 413 | </listitem>
|
|---|
| 414 | </varlistentry>
|
|---|
| 415 |
|
|---|
| 416 | <varlistentry id="gcc-ar">
|
|---|
| 417 | <term><command>gcc-ar</command></term>
|
|---|
| 418 | <listitem>
|
|---|
| 419 | <para>A wrapper around <command>ar</command> that adds a
|
|---|
| 420 | plugin to the command line. This program is only used
|
|---|
| 421 | to add "link time optimization" and is not useful with the
|
|---|
| 422 | default build options.</para>
|
|---|
| 423 | <indexterm zone="ch-system-gcc gcc-ar">
|
|---|
| 424 | <primary sortas="b-gcc-ar">gc-ar</primary>
|
|---|
| 425 | </indexterm>
|
|---|
| 426 | </listitem>
|
|---|
| 427 | </varlistentry>
|
|---|
| 428 |
|
|---|
| 429 | <varlistentry id="gcc-nm">
|
|---|
| 430 | <term><command>gcc-nm</command></term>
|
|---|
| 431 | <listitem>
|
|---|
| 432 | <para>A wrapper around <command>nm</command> that adds a
|
|---|
| 433 | plugin to the command line. This program is only used
|
|---|
| 434 | to add "link time optimization" and is not useful with the
|
|---|
| 435 | default build options.</para>
|
|---|
| 436 | <indexterm zone="ch-system-gcc gcc-nm">
|
|---|
| 437 | <primary sortas="b-gcc-nm">gc-nm</primary>
|
|---|
| 438 | </indexterm>
|
|---|
| 439 | </listitem>
|
|---|
| 440 | </varlistentry>
|
|---|
| 441 |
|
|---|
| 442 | <varlistentry id="gcc-ranlib">
|
|---|
| 443 | <term><command>gcc-ranlib</command></term>
|
|---|
| 444 | <listitem>
|
|---|
| 445 | <para>A wrapper around <command>ranlib</command> that adds a
|
|---|
| 446 | plugin to the command line. This program is only used
|
|---|
| 447 | to add "link time optimization" and is not useful with the
|
|---|
| 448 | default build options.</para>
|
|---|
| 449 | <indexterm zone="ch-system-gcc gcc-ranlib">
|
|---|
| 450 | <primary sortas="b-gcc-ranlib">gc-ranlib</primary>
|
|---|
| 451 | </indexterm>
|
|---|
| 452 | </listitem>
|
|---|
| 453 | </varlistentry>
|
|---|
| 454 |
|
|---|
| 455 | <varlistentry id="gcov">
|
|---|
| 456 | <term><command>gcov</command></term>
|
|---|
| 457 | <listitem>
|
|---|
| 458 | <para>A coverage testing tool; it is used to analyze programs to
|
|---|
| 459 | determine where optimizations will have the greatest effect</para>
|
|---|
| 460 | <indexterm zone="ch-system-gcc gcov">
|
|---|
| 461 | <primary sortas="b-gcov">gcov</primary>
|
|---|
| 462 | </indexterm>
|
|---|
| 463 | </listitem>
|
|---|
| 464 | </varlistentry>
|
|---|
| 465 |
|
|---|
| 466 | <varlistentry id="gcov-dump">
|
|---|
| 467 | <term><command>gcov-dump</command></term>
|
|---|
| 468 | <listitem>
|
|---|
| 469 | <para>Offline gcda and gcno profile dump tool</para>
|
|---|
| 470 | <indexterm zone="ch-system-gcc gcov-dump">
|
|---|
| 471 | <primary sortas="b-gcov-dump">gcov-dump</primary>
|
|---|
| 472 | </indexterm>
|
|---|
| 473 | </listitem>
|
|---|
| 474 | </varlistentry>
|
|---|
| 475 |
|
|---|
| 476 | <varlistentry id="gcov-tool">
|
|---|
| 477 | <term><command>gcov-tool</command></term>
|
|---|
| 478 | <listitem>
|
|---|
| 479 | <para>Offline gcda profile processing tool</para>
|
|---|
| 480 | <indexterm zone="ch-system-gcc gcov-tool">
|
|---|
| 481 | <primary sortas="b-gcov-tool">gcov-tool</primary>
|
|---|
| 482 | </indexterm>
|
|---|
| 483 | </listitem>
|
|---|
| 484 | </varlistentry>
|
|---|
| 485 |
|
|---|
| 486 | <varlistentry id="lto-dump">
|
|---|
| 487 | <term><command>lto-dump</command></term>
|
|---|
| 488 | <listitem>
|
|---|
| 489 | <para>Tool for dumping object files produced by GCC with LTO
|
|---|
| 490 | enabled</para>
|
|---|
| 491 | <indexterm zone="ch-system-gcc lto-dump">
|
|---|
| 492 | <primary sortas="b-lto-dump">lto-dump</primary>
|
|---|
| 493 | </indexterm>
|
|---|
| 494 | </listitem>
|
|---|
| 495 | </varlistentry>
|
|---|
| 496 |
|
|---|
| 497 | <varlistentry id="libasan">
|
|---|
| 498 | <term><filename class="libraryfile">libasan</filename></term>
|
|---|
| 499 | <listitem>
|
|---|
| 500 | <para>The Address Sanitizer runtime library</para>
|
|---|
| 501 | <indexterm zone="ch-system-gcc libasan">
|
|---|
| 502 | <primary sortas="b-libasan">libasan</primary>
|
|---|
| 503 | </indexterm>
|
|---|
| 504 | </listitem>
|
|---|
| 505 | </varlistentry>
|
|---|
| 506 |
|
|---|
| 507 | <varlistentry id="libatomic">
|
|---|
| 508 | <term><filename class="libraryfile">libatomic</filename></term>
|
|---|
| 509 | <listitem>
|
|---|
| 510 | <para>GCC atomic built-in runtime library</para>
|
|---|
| 511 | <indexterm zone="ch-system-gcc libatomic">
|
|---|
| 512 | <primary sortas="b-libatomic">libatomic</primary>
|
|---|
| 513 | </indexterm>
|
|---|
| 514 | </listitem>
|
|---|
| 515 | </varlistentry>
|
|---|
| 516 |
|
|---|
| 517 | <varlistentry id="libcc1">
|
|---|
| 518 | <term><filename class="libraryfile">libcc1</filename></term>
|
|---|
| 519 | <listitem>
|
|---|
| 520 | <para>A library that allows GDB to make use of GCC</para>
|
|---|
| 521 | <indexterm zone="ch-system-gcc libcc1">
|
|---|
| 522 | <primary sortas="b-libcc1">libcc1</primary>
|
|---|
| 523 | </indexterm>
|
|---|
| 524 | </listitem>
|
|---|
| 525 | </varlistentry>
|
|---|
| 526 |
|
|---|
| 527 | <varlistentry id="libgcc">
|
|---|
| 528 | <term><filename class="libraryfile">libgcc</filename></term>
|
|---|
| 529 | <listitem>
|
|---|
| 530 | <para>Contains run-time support for <command>gcc</command></para>
|
|---|
| 531 | <indexterm zone="ch-system-gcc libgcc">
|
|---|
| 532 | <primary sortas="c-libgcc">libgcc</primary>
|
|---|
| 533 | </indexterm>
|
|---|
| 534 | </listitem>
|
|---|
| 535 | </varlistentry>
|
|---|
| 536 |
|
|---|
| 537 | <varlistentry id="libgcov">
|
|---|
| 538 | <term><filename class="libraryfile">libgcov</filename></term>
|
|---|
| 539 | <listitem>
|
|---|
| 540 | <para>This library is linked into a program when GCC is instructed
|
|---|
| 541 | to enable profiling</para>
|
|---|
| 542 | <indexterm zone="ch-system-gcc libgcov">
|
|---|
| 543 | <primary sortas="c-libgcov">libgcov</primary>
|
|---|
| 544 | </indexterm>
|
|---|
| 545 | </listitem>
|
|---|
| 546 | </varlistentry>
|
|---|
| 547 |
|
|---|
| 548 | <varlistentry id="libgomp">
|
|---|
| 549 | <term><filename class="libraryfile">libgomp</filename></term>
|
|---|
| 550 | <listitem>
|
|---|
| 551 | <para>GNU implementation of the OpenMP API for multi-platform
|
|---|
| 552 | shared-memory parallel programming in C/C++ and Fortran</para>
|
|---|
| 553 | <indexterm zone="ch-system-gcc libgomp">
|
|---|
| 554 | <primary sortas="c-libgomp">libgomp</primary>
|
|---|
| 555 | </indexterm>
|
|---|
| 556 | </listitem>
|
|---|
| 557 | </varlistentry>
|
|---|
| 558 |
|
|---|
| 559 | <varlistentry id="libhwasan">
|
|---|
| 560 | <term><filename class="libraryfile">libhwasan</filename></term>
|
|---|
| 561 | <listitem>
|
|---|
| 562 | <para>The Hardware-assisted Address Sanitizer runtime library</para>
|
|---|
| 563 | <indexterm zone="ch-system-gcc libhwasan">
|
|---|
| 564 | <primary sortas="c-libhwasan">libhwasan</primary>
|
|---|
| 565 | </indexterm>
|
|---|
| 566 | </listitem>
|
|---|
| 567 | </varlistentry>
|
|---|
| 568 |
|
|---|
| 569 | <varlistentry id="libitm">
|
|---|
| 570 | <term><filename class="libraryfile">libitm</filename></term>
|
|---|
| 571 | <listitem>
|
|---|
| 572 | <para>The GNU transactional memory library</para>
|
|---|
| 573 | <indexterm zone="ch-system-gcc libitm">
|
|---|
| 574 | <primary sortas="c-libitm">libitm</primary>
|
|---|
| 575 | </indexterm>
|
|---|
| 576 | </listitem>
|
|---|
| 577 | </varlistentry>
|
|---|
| 578 |
|
|---|
| 579 | <varlistentry id="liblsan">
|
|---|
| 580 | <term><filename class="libraryfile">liblsan</filename></term>
|
|---|
| 581 | <listitem>
|
|---|
| 582 | <para>The Leak Sanitizer runtime library</para>
|
|---|
| 583 | <indexterm zone="ch-system-gcc liblsan">
|
|---|
| 584 | <primary sortas="c-liblsan">liblsan</primary>
|
|---|
| 585 | </indexterm>
|
|---|
| 586 | </listitem>
|
|---|
| 587 | </varlistentry>
|
|---|
| 588 |
|
|---|
| 589 | <varlistentry id="liblto_plugin">
|
|---|
| 590 | <term><filename class="libraryfile">liblto_plugin</filename></term>
|
|---|
| 591 | <listitem>
|
|---|
| 592 | <para>GCC's LTO plugin allows Binutils to process object files
|
|---|
| 593 | produced by GCC with LTO enabled</para>
|
|---|
| 594 | <indexterm zone="ch-system-gcc liblto_plugin">
|
|---|
| 595 | <primary sortas="c-liblto_plugin">liblto_plugin</primary>
|
|---|
| 596 | </indexterm>
|
|---|
| 597 | </listitem>
|
|---|
| 598 | </varlistentry>
|
|---|
| 599 |
|
|---|
| 600 | <varlistentry id="libquadmath">
|
|---|
| 601 | <term><filename class="libraryfile">libquadmath</filename></term>
|
|---|
| 602 | <listitem>
|
|---|
| 603 | <para>GCC Quad Precision Math Library API</para>
|
|---|
| 604 | <indexterm zone="ch-system-gcc libquadmath">
|
|---|
| 605 | <primary sortas="c-libquadmath">libquadmath</primary>
|
|---|
| 606 | </indexterm>
|
|---|
| 607 | </listitem>
|
|---|
| 608 | </varlistentry>
|
|---|
| 609 |
|
|---|
| 610 | <varlistentry id="libssp">
|
|---|
| 611 | <term><filename class="libraryfile">libssp</filename></term>
|
|---|
| 612 | <listitem>
|
|---|
| 613 | <para>Contains routines supporting GCC's stack-smashing protection
|
|---|
| 614 | functionality. Normally it is not used, because Glibc also provides
|
|---|
| 615 | those routines.</para>
|
|---|
| 616 | <indexterm zone="ch-system-gcc libssp">
|
|---|
| 617 | <primary sortas="c-libssp">libssp</primary>
|
|---|
| 618 | </indexterm>
|
|---|
| 619 | </listitem>
|
|---|
| 620 | </varlistentry>
|
|---|
| 621 |
|
|---|
| 622 | <varlistentry id="libstdc">
|
|---|
| 623 | <term><filename class="libraryfile">libstdc++</filename></term>
|
|---|
| 624 | <listitem>
|
|---|
| 625 | <para>The standard C++ library</para>
|
|---|
| 626 | <indexterm zone="ch-system-gcc libstdc">
|
|---|
| 627 | <primary sortas="c-libstdc++">libstdc++</primary>
|
|---|
| 628 | </indexterm>
|
|---|
| 629 | </listitem>
|
|---|
| 630 | </varlistentry>
|
|---|
| 631 |
|
|---|
| 632 | <varlistentry id="libstdcexp">
|
|---|
| 633 | <term><filename class="libraryfile">libstdc++exp</filename></term>
|
|---|
| 634 | <listitem>
|
|---|
| 635 | <para>Experimental C++ Contracts library</para>
|
|---|
| 636 | <indexterm zone="ch-system-gcc libstdcexp">
|
|---|
| 637 | <primary sortas="c-libstdc++exp">libstdc++exp</primary>
|
|---|
| 638 | </indexterm>
|
|---|
| 639 | </listitem>
|
|---|
| 640 | </varlistentry>
|
|---|
| 641 |
|
|---|
| 642 | <varlistentry id="libstdcfs">
|
|---|
| 643 | <term><filename class="libraryfile">libstdc++fs</filename></term>
|
|---|
| 644 | <listitem>
|
|---|
| 645 | <para>ISO/IEC TS 18822:2015 Filesystem library</para>
|
|---|
| 646 | <indexterm zone="ch-system-gcc libstdcfs">
|
|---|
| 647 | <primary sortas="c-libstdc++fs">libstdc++fs</primary>
|
|---|
| 648 | </indexterm>
|
|---|
| 649 | </listitem>
|
|---|
| 650 | </varlistentry>
|
|---|
| 651 |
|
|---|
| 652 | <varlistentry id="libsupc">
|
|---|
| 653 | <term><filename class="libraryfile">libsupc++</filename></term>
|
|---|
| 654 | <listitem>
|
|---|
| 655 | <para>Provides supporting routines for the C++ programming
|
|---|
| 656 | language</para>
|
|---|
| 657 | <indexterm zone="ch-system-gcc libsupc">
|
|---|
| 658 | <primary sortas="c-libsupc++">libsupc++</primary>
|
|---|
| 659 | </indexterm>
|
|---|
| 660 | </listitem>
|
|---|
| 661 | </varlistentry>
|
|---|
| 662 |
|
|---|
| 663 | <varlistentry id="libtsan">
|
|---|
| 664 | <term><filename class="libraryfile">libtsan</filename></term>
|
|---|
| 665 | <listitem>
|
|---|
| 666 | <para>The Thread Sanitizer runtime library</para>
|
|---|
| 667 | <indexterm zone="ch-system-gcc libtsan">
|
|---|
| 668 | <primary sortas="c-libtsan">libtsan</primary>
|
|---|
| 669 | </indexterm>
|
|---|
| 670 | </listitem>
|
|---|
| 671 | </varlistentry>
|
|---|
| 672 |
|
|---|
| 673 | <varlistentry id="libubsan">
|
|---|
| 674 | <term><filename class="libraryfile">libubsan</filename></term>
|
|---|
| 675 | <listitem>
|
|---|
| 676 | <para>The Undefined Behavior Sanitizer runtime library</para>
|
|---|
| 677 | <indexterm zone="ch-system-gcc libubsan">
|
|---|
| 678 | <primary sortas="c-libubsan">libubsan</primary>
|
|---|
| 679 | </indexterm>
|
|---|
| 680 | </listitem>
|
|---|
| 681 | </varlistentry>
|
|---|
| 682 |
|
|---|
| 683 | </variablelist>
|
|---|
| 684 |
|
|---|
| 685 | </sect2>
|
|---|
| 686 |
|
|---|
| 687 | </sect1>
|
|---|
