Automatic merge of trunk into multilib

This commit is contained in:
Thomas Trepl 2023-04-17 00:30:13 +02:00
commit 796b226aa2
3 changed files with 20 additions and 9 deletions

View File

@ -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>

View File

@ -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>

View File

@ -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>