Changeset ec36fac for chapter08

Timestamp:

02/27/2024 03:39:33 PM (7 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/loongarch, xry111/loongarch-12.1, xry111/loongarch-12.2

Children:

09f2a24

Parents:

4ac095c7 (diff), 23f4367 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

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

Location:

chapter08

Files:

• coreutils.xml (modified) (1 diff)
• expect.xml (modified) (1 diff)
• gcc.xml (modified) (2 diffs)
• glibc.xml (modified) (4 diffs)
• libxcrypt.xml (modified) (1 diff)
• pkgconf.xml (modified) (1 diff)
• procps.xml (modified) (1 diff)
• systemd.xml (modified) (1 diff)
• vim.xml (modified) (1 diff)

chapter08/coreutils.xml

@@ -130 +130 @@
 <!-- Sometimes skipped, but if not it may fail.
      Please DO NOT remove or comment out this unless we can fully
-     understand it!  -->
+     understand it!
     <para>The test-getlogin test may fail in the LFS chroot environment.</para>
+    20240226: Commented out as it seems the upstream has root-caused and
+    fixed the issue.  I've checked the fix is in Coreutils 9.4 release
+    tarball:
+
+    https://lists.gnu.org/archive/html/bug-gnulib/2022-06/msg00079.html
+-->
 
     <para>Remove the temporary group:</para>

chapter08/expect.xml

@@ -64 +64 @@
     the chroot environment following <xref linkend='ch-tools-chroot'/>.
     This issue needs to be resolved before continuing, or the test suites
-    requring Expect (for example the test suites of Bash, Binutils, GCC,
+    requiring Expect (for example the test suites of Bash, Binutils, GCC,
     GDBM, and of course Expect itself) will fail catastrophically, and other
     subtle breakages may also happen.</para>

chapter08/gcc.xml

@@ -189 +189 @@
 
     <para>
-      With Glibc-2.38, the analyzer tests named
-      <filename>data-model-4.c</filename> and
-      <filename>conftest-1.c</filename> 
-        are known to fail.
-      In the asan tests, several tests in <filename>asan_test.C</filename> 
-        are known to fail.
-      The test named <filename>interception-malloc-test-1.C</filename> 
-        is known to fail.
+    Seven tests in the <filename class='directory'>analyzer</filename>
+    directory are known to fail.
+
+    For g++, 21 tests (out of approximately 250,000): 14
+    <quote>AddressSanitizer*</quote>
+    tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
+    known to fail.
     </para>
 
@@ -203 +202 @@
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>
-
-    <!--note><para>
-      On some combinations of kernel configuration and AMD processors
-      there may be more than 1100 failures in the gcc.target/i386/mpx
-      tests (which are designed to test the MPX option on recent
-      Intel processors). These can safely be ignored on AMD
-      processors. These tests will also fail on Intel processors if MPX support
-      is not enabled in the kernel even though it is present on the CPU.
-    </para></note-->
 
     <para>Install the package:</para>

chapter08/glibc.xml

@@ -164 +164 @@
       </listitem>
 
-<!-- Did not fail with glibc-2.38
-      <listitem>
-        <para><emphasis>misc/tst-ttyname</emphasis>
-        is known to fail in the LFS chroot environment.</para>
-      </listitem>
--->
-
-      <!-- https://sourceware.org/pipermail/libc-alpha/2022-August/141567.html -->
-      <listitem>
-        <para>The <emphasis>stdlib/tst-arc4random-thread</emphasis>
-        test is known to fail if the host kernel is relatively old.</para>
-      </listitem>
-
       <listitem>
         <para>Some tests, for example
-        <emphasis>nss/tst-nss-files-hosts-multi</emphasis>,
-        are known to fail on relatively slow systems due to an internal
-        timeout.</para>
+        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> and
+        <emphasis>nptl/tst-thread-affinity*</emphasis>
+        are known to fail due to a timeout (especially when the system is
+        relatively slow and/or running the test suite with multiple
+        parallel make jobs).  These tests can be identified with:</para>
+
+        <!-- TODO: Using nodump for freeze.  Change it to role="test" after
+             12.1 release so jhalfs can list these in the log.  -->
+        <screen role="nodump"><userinput>grep "Timed out" -l $(find -name \*.out)</userinput></screen>
+
+        <para>It's possible to re-run a single test with enlarged timeout
+        with
+        <command>TIMEOUTFACTOR=<replaceable>&lt;factor&gt;</replaceable>
+        make test t=<replaceable>&lt;test name&gt;</replaceable></command>.
+        For example, <command>TIMEOUTFACTOR=10 make test
+        t=nss/tst-nss-files-hosts-multi</command> will re-run
+        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> with ten times
+        the original timeout.</para>
       </listitem>
 
       <listitem>
         <para>Additionally, some tests may fail with a relatively old CPU
-        model or host kernel version.</para>
+        model (for example
+        <emphasis>elf/tst-cpu-features-cpuinfo</emphasis>) or host kernel
+        version (for example
+        <emphasis>stdlib/tst-arc4random-thread</emphasis>).</para>
       </listitem>
     </itemizedlist>
@@ -236 +241 @@
             section to install
             <filename class='libraryfile'>libcrypt.so.1*</filename>
-            (overwritting
+            (replacing
             <filename class='libraryfile'>libcrypt.so.1</filename> from the
             prior Glibc installation)</emphasis>.
@@ -254 +259 @@
           <screen role='nodump'><userinput>rm -f /usr/sbin/nscd</userinput></screen>
 
-          <para>
+          <para revision='systemd'>
             If this system (prior to LFS 12.1, exclusive) is based on
             Systemd, it's also needed to disable and stop the
@@ -531 +536 @@
         <listitem>
           <para>This creates the <filename>posixrules</filename> file. We use
-          New York because POSIX requires the daylight savings time rules
+          New York because POSIX requires the daylight saving time rules
           to be in accordance with US rules.</para>
         </listitem>

chapter08/libxcrypt.xml

@@ -111 +111 @@
             --disable-failure-tokens
 make
-cp -av .libs/libcrypt.so.1* /usr/lib</userinput></screen>
+cp -av --remove-destination .libs/libcrypt.so.1* /usr/lib</userinput></screen>
     </note>
 

chapter08/pkgconf.xml

@@ -44 +44 @@
 
     <title>Installation of Pkgconf</title>
-
-    <!-- https://github.com/pkgconf/pkgconf/issues/317 -->
-    <para>Fix a regression in pkgconf-2.1.0 breaking BLFS packages:</para>
-
-    <screen><userinput remap="pre">patch -Np1 -i ../&pkgconf-upstream-fix-patch;</userinput></screen>
 
     <para>Prepare Pkgconf for compilation:</para>

chapter08/procps.xml

@@ -73 +73 @@
     <para> To run the test suite, run:</para>
 
-<screen><userinput remap="test">make check</userinput></screen>
+<screen><userinput remap="test">make -k check</userinput></screen>
+
+    <para>One test named
+    <literal>ps with output flag bsdtime,cputime,etime,etimes</literal>
+    is known to fail if the host kernel is not built with
+    <literal>CONFIG_BSD_PROCESS_ACCT</literal> enabled.
+    <!-- These two tests just do not work as root but they seem to pass
+         in most time due to some internal hazards of Tcl/Expect/DejaGNU
+         framework.  However the failures have been really observed.
+         TODO: run the test suite as tester after the freeze ends.  -->
+    Two tests named
+    <literal>pmap X with unreachable process</literal> and
+    <literal>pmap XX with unreachable process</literal> are known to
+    fail occasionally.</para>
 
     <para>Install the package:</para>

chapter08/systemd.xml

@@ -51 +51 @@
     <!-- https://github.com/systemd/systemd/pull/30549 -->
     <para>Now fix a security vulnerability in the DNSSEC verification of
-    <command>systemd-resolved</command>:</para>
-
-<screen><userinput remap='pre'>sed -e '/return FLAGS_SET.*AUTHENTICATED/s/(t/(dt/' \
-    -i src/resolve/resolved-dns-transaction.c</userinput></screen>
+    <command>systemd-resolved</command> and a bug breaking running
+    <command>systemd-analyze verify</command> on an instantiated systemd
+    unit:</para>
+
+<screen><userinput remap='pre'>patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen>
 
     <para>Prepare systemd for compilation:</para>

chapter08/vim.xml

@@ -72 +72 @@
     class="username">tester</systemitem>:</para>
 
-<screen><userinput remap="test">su tester -c "LANG=en_US.UTF-8 make -j1 test" &amp;> vim-test.log</userinput></screen>
+<screen><userinput remap="test">su tester -c "TERM=xterm-256color LANG=en_US.UTF-8 make -j1 test" \
+   &amp;> vim-test.log</userinput></screen>
 
     <para>The test suite outputs a lot of binary data to the screen.  This can
-    cause issues with the settings of the current terminal.  The problem can be
+    cause issues with the settings of the current terminal (especially while
+    we are overriding the <envar>TERM</envar> variable to satisify some
+    assumptions of the test suite).  The problem can be
     avoided by redirecting the output to a log file as shown above.  A
-    successful test will result in the words "ALL DONE" in the log file
-    at completion.</para>
+    successful test will result in the words <computeroutput>ALL
+    DONE</computeroutput> in the log file at completion.</para>
 
     <para>Install the package:</para>