Merge remote-tracking branch 'origin/trunk' into xry111/arm64

This commit is contained in:
Xi Ruoyao 2022-10-03 19:08:38 +08:00
commit 1dcfd5039d
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
2 changed files with 13 additions and 11 deletions

View File

@ -160,20 +160,22 @@ cd build</userinput></screen>
<screen><userinput remap="test">make -k check</userinput></screen>
<para>
Some gprofng tests depend on hardware and may fail on AArch64.
<!-- Happens for me with -j24, not sure if it's aarch64-only -->
Some GAS tests may fail if the test is run parallelly due to a race
condition.
</para>
<para>
<!-- Caused by egrep deprecation. Note that we don't "patch" temp grep.
And it seems unworthy to add a sed into temp grep just for one test
failure. (I don't really agree to "patch" grep in the first place,
anyway.) -->
The test named <filename>ar with versioned solib</filename> is also
known to fail.</para>
anyway.)
Will be fixed in 2.40 (upstream commit 67d1991). -->
The test named <filename>ar with versioned solib</filename> is
known to fail.
<!-- https://sourceware.org/bugzilla/show_bug.cgi?id=29107 -->
Because of a race between the gas testsuite and the gprofng testsuite,
some gas tests may fail if parallel jobs are used. If you are not
assured of the correctness of gas, invoke
<command>make check-gas</command> to run gas testsuite separately and
all tests should pass. Three gprofng tests result
<literal>ERROR</literal> and they are counted as
<literal>UNRESOLVED</literal> in the summary.</para>
<para>Install the package:</para>

View File

@ -151,7 +151,7 @@ esac</userinput></screen>
<para>You may see some test failures. The Glibc test suite is
somewhat dependent on the host system. A few failures out of
over 4200 tests can generally be ignored. This is a list of the
over 5000 tests can generally be ignored. This is a list of the
most common issues seen for recent versions of LFS:</para>
<itemizedlist>