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