diff options
Diffstat (limited to 'chapter08/gcc.xml')
| -rw-r--r-- | chapter08/gcc.xml | 51 |
1 files changed, 41 insertions, 10 deletions
diff --git a/chapter08/gcc.xml b/chapter08/gcc.xml index 546ad6b1a..df5a0ff07 100644 --- a/chapter08/gcc.xml +++ b/chapter08/gcc.xml @@ -78,7 +78,7 @@ cd build</userinput></screen> --enable-default-ssp \ --disable-multilib \ --disable-bootstrap \ - --disable-fixinclude \ + --disable-fixincludes \ --with-system-zlib</userinput></screen> <para>GCC supports seven different computer languages, but the @@ -99,6 +99,17 @@ cd build</userinput></screen> </varlistentry> <varlistentry> + <term><parameter>--disable-fixincludes</parameter></term> + <listitem> + <para>By default, during the installation of GCC some system + headers would be <quote>fixed</quote> to be used with GCC. This + is not necessary for a modern Linux system, and potentionally + harmful if a package is reinstalled after installing GCC. This + switch prevents GCC from <quote>fixing</quote> the headers.</para> + </listitem> + </varlistentry> + + <varlistentry> <term><parameter>--with-system-zlib</parameter></term> <listitem> <para>This switch tells GCC to link to the system installed copy of @@ -161,13 +172,13 @@ su tester -c "PATH=$PATH make -k check"</userinput></screen> url="&test-results;"/> and <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para> - <para>Eleven tests in the i386 test suite for the gcc compiler are known to FAIL. - It's because the test files do not account for the - <parameter>--enable-default-pie</parameter> option.</para> - - <para>Four tests related to PR100400 may be reported - as both XPASS and FAIL when testing the g++ compiler; the test file - is not well written.</para> + <para>Two tests named <filename>pr104610.c</filename> and + <filename>pr69482-1.c</filename> are known to fail because the test + files does not account for the + <parameter>--enable-default-ssp</parameter> option. + <!-- https://gcc.gnu.org/PR106375 and https://gcc.gnu.org/PR109353 --> + Additionally, two tests named <filename>copy.cc</filename> and + <filename>pr56837.c</filename> are known to fail.</para> <para>A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet. @@ -335,10 +346,10 @@ mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen> and lto-dump</seg> <seg>libasan.{a,so}, libatomic.{a,so}, libcc1.so, libgcc.a, libgcc_eh.a, - libgcc_s.so, libgcov.a, libgomp.{a,so}, libitm.{a,so}, + libgcc_s.so, libgcov.a, libgomp.{a,so}, libhwasan.{a,so}, libitm.{a,so}, liblsan.{a,so}, liblto_plugin.so, libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a, - libstdc++.{a,so}, libstdc++fs.a, libsupc++.a, libtsan.{a,so}, + libstdc++.{a,so}, libstdc++exp.a, libstdc++fs.a, libsupc++.a, libtsan.{a,so}, and libubsan.{a,so}</seg> <seg>/usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, and @@ -545,6 +556,16 @@ mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen> </listitem> </varlistentry> + <varlistentry id="libhwasan"> + <term><filename class="libraryfile">libhwasan</filename></term> + <listitem> + <para>The Hardware-assisted Address Sanitizer runtime library</para> + <indexterm zone="ch-system-gcc libhwasan"> + <primary sortas="c-libhwasan">libhwasan</primary> + </indexterm> + </listitem> + </varlistentry> + <varlistentry id="libitm"> <term><filename class="libraryfile">libitm</filename></term> <listitem> @@ -608,6 +629,16 @@ mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib</userinput></screen> </listitem> </varlistentry> + <varlistentry id="libstdcexp"> + <term><filename class="libraryfile">libstdc++exp</filename></term> + <listitem> + <para>Experimental C++ Contracts library</para> + <indexterm zone="ch-system-gcc libstdcexp"> + <primary sortas="c-libstdc++exp">libstdc++exp</primary> + </indexterm> + </listitem> + </varlistentry> + <varlistentry id="libstdcfs"> <term><filename class="libraryfile">libstdc++fs</filename></term> <listitem> |