diff options
Diffstat (limited to 'chapter08')
-rw-r--r-- | chapter08/dbus.xml | 12 | ||||
-rw-r--r-- | chapter08/gcc.xml | 51 | ||||
-rw-r--r-- | chapter08/openssl.xml | 11 | ||||
-rw-r--r-- | chapter08/psmisc.xml | 4 | ||||
-rw-r--r-- | chapter08/util-linux.xml | 6 |
5 files changed, 64 insertions, 20 deletions
diff --git a/chapter08/dbus.xml b/chapter08/dbus.xml index 8f3c80f7a..f59dd122b 100644 --- a/chapter08/dbus.xml +++ b/chapter08/dbus.xml @@ -79,10 +79,14 @@ <screen><userinput remap="make">make</userinput></screen> - <para>This package does come with a test suite, but it requires several + <para>To test the results, issue:</para> + +<screen><userinput remap="test">make check</userinput></screen> + + <para>Many tests are disabled because they require additional packages that are not included in LFS. Instructions for running the - test suite can be found in the BLFS book at - <ulink url="&blfs-book;general/dbus.html"/>.</para> + comprehensive test suite can be found in + <ulink url="&blfs-book;general/dbus.html">the BLFS book</ulink>.</para> <para>Install the package:</para> @@ -107,7 +111,7 @@ <seg>dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor, dbus-run-session, dbus-send, dbus-test-tool, dbus-update-activation-environment, and dbus-uuidgen</seg> - <seg>libdbus-1.{a,so}</seg> + <seg>libdbus-1.so</seg> <seg>/etc/dbus-1, /usr/include/dbus-1.0, /usr/lib/dbus-1.0, /usr/share/dbus-1, /usr/share/doc/dbus-&dbus-version;, and /var/lib/dbus</seg> 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> diff --git a/chapter08/openssl.xml b/chapter08/openssl.xml index 0c3c41a7c..40a769311 100644 --- a/chapter08/openssl.xml +++ b/chapter08/openssl.xml @@ -65,10 +65,13 @@ <screen><userinput remap="test">make test</userinput></screen> - <para>One test, 30-test_afalg.t, is known to fail on some kernel - configurations (depending on inconsistent values of - CONFIG_CRYPTO_USER_API* settings.) If it fails, it can safely be - ignored.</para> + <para>One test, 30-test_afalg.t, is known to fail if the host kernel + does not have <option>CONFIG_CRYPTO_USER_API_SKCIPHER</option> enabled, + or does not have any options providing an AES with CBC implementation + (for example, the combination of <option>CONFIG_CRYPTO_AES</option> + and <option>CONFIG_CRYPTO_CBC</option>, or + <option>CONFIG_CRYPTO_AES_NI_INTEL</option> if the CPU supports AES-NI) + enabled. If it fails, it can safely be ignored.</para> <para>Install the package:</para> diff --git a/chapter08/psmisc.xml b/chapter08/psmisc.xml index 6a826202d..cbf7609f3 100644 --- a/chapter08/psmisc.xml +++ b/chapter08/psmisc.xml @@ -49,7 +49,9 @@ <screen><userinput remap="make">make</userinput></screen> - <para>This package does not come with a test suite.</para> + <para>To run the test suite, run:</para> + +<screen><userinput remap="test">make check</userinput></screen> <para>Install the package:</para> diff --git a/chapter08/util-linux.xml b/chapter08/util-linux.xml index ccf8b3cd0..44d55697d 100644 --- a/chapter08/util-linux.xml +++ b/chapter08/util-linux.xml @@ -101,7 +101,11 @@ su tester -c "make -k check"</userinput></screen> <para>The <emphasis>hardlink</emphasis> tests will fail if the host's kernel - does not have the option CONFIG_CRYPTO_USER_API_HASH set. In addition, + does not have the option <option>CONFIG_CRYPTO_USER_API_HASH</option> + enabled or does not have any options providing a SHA256 implementation + (for example, <option>CONFIG_CRYPTO_SHA256</option>, or + <option>CONFIG_CRYPTO_SHA256_SSSE3</option> if the CPU supports + Supplemental SSE3) enabled. In addition, two sub-tests from misc: mbsencode and one sub-test from script: replay are known to fail.</para> |