Changeset 2001f5c for chapter08/coreutils.xml
- Timestamp:
- 03/01/2024 04:03:28 PM (7 months ago)
- Branches:
- 12.2, 12.2-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib
- Children:
- 0566a05, a56a4fc, f0d0a00
- Parents:
- c2d820a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/coreutils.xml
rc2d820a r2001f5c 124 124 <screen><userinput remap="test">chown -R tester . </userinput></screen> 125 125 126 <para>Now run the tests:</para> 127 128 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"</userinput></screen> 129 130 <!-- Sometimes skipped, but if not it may fail. 131 Please DO NOT remove or comment out this unless we can fully 132 understand it! 133 <para>The test-getlogin test may fail in the LFS chroot environment.</para> 134 20240226: Commented out as it seems the upstream has root-caused and 135 fixed the issue. I've checked the fix is in Coreutils 9.4 release 136 tarball: 137 138 https://lists.gnu.org/archive/html/bug-gnulib/2022-06/msg00079.html 139 --> 126 <!-- To editors: in jhalfs the standard input is always piped to "make" 127 so the test failures are not reproducible in jhalfs even if 128 running the build in a PTY. Don't use jhalfs to test if we can 129 remove < /dev/null. --> 130 <para>Now run the tests (using <filename>/dev/null</filename> for the 131 standard input, or two tests may be broken if building LFS in a 132 graphical terminal or a session in SSH or GNU Screen etc. because the 133 standard input is connected to a PTY from host distro, and the device 134 node for such a PTY cannot be accessed from the LFS chroot 135 environment):</para> 136 137 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check" < /dev/null</userinput></screen> 140 138 141 139 <para>Remove the temporary group:</para>
Note:
See TracChangeset
for help on using the changeset viewer.