gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-11 14:54:17 +01:00
Code Issues Packages Projects Releases Wiki Activity

Automatic merge of trunk into multilib

Browse Source
This commit is contained in:
Thomas Trepl 2024-02-27 00:30:19 +01:00
commit 79b32d358b
3 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
chapter08/coreutils.xml
View File

@ -129,8 +129,14 @@ FORCE_UNSAFE_CONFIGURE=1 ./configure \
<!-- Sometimes skipped, but if not it may fail. <!-- Sometimes skipped, but if not it may fail.
Please DO NOT remove or comment out this unless we can fully 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> <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> <para>Remove the temporary group:</para>

5
chapter08/procps.xml
View File

@ -74,7 +74,10 @@
<screen><userinput remap="test">make check</userinput></screen> <screen><userinput remap="test">make check</userinput></screen>
<para>One test in the "ps" tests is known to fail.</para> <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.</para>
<para>Install the package:</para> <para>Install the package:</para>

4
chapter08/vim.xml
View File

@ -79,8 +79,8 @@
we are overriding the <envar>TERM</envar> variable to satisify some we are overriding the <envar>TERM</envar> variable to satisify some
assumptions of the test suite). The problem can be assumptions of the test suite). The problem can be
avoided by redirecting the output to a log file as shown above. A 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 successful test will result in the words <computeroutput>ALL
at completion.</para> DONE</computeroutput> in the log file at completion.</para>
<para>Install the package:</para> <para>Install the package:</para>