Changeset 76db8d6 for chapter06/gcc.xml

Timestamp:

08/12/2018 04:35:49 PM (6 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

3b03219

Parents:

059c79e

Message:

Add LANG to vim test instructions.
Ensure grep tests run to completion.
Run gcc tests in Chapter 6 as a non-privileged user.

Move shadow to before gcc so the gcc tests can
use su to run as a non-privileged user.

Add perl Configure options in Chapter 5 to ensure
no host system libraries are used.

Update minimum make version to 4.0 required by glibc-2.28.
Update bzip2 url to a new location.
Update to linux-4.17.14.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11446 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter06/gcc.xml (modified) (2 diffs)

chapter06/gcc.xml

@@ -110 +110 @@
 <screen><userinput remap="test">ulimit -s 32768</userinput></screen>
 
-    <para>Test the results, but do not stop at errors:</para>
-
-<screen><userinput remap="test">make -k check</userinput></screen>
+    <para>Remove one test known to cause a problem:</para>
+
+<screen><userinput remap="test">rm ../gcc/testsuite/g++.dg/pr83239.C</userinput></screen>
+
+    <para>Test the results as a non-privileged user, but do not stop at errors:</para>
+
+<screen><userinput remap="test">chown -Rv nobody . 
+su nobody -s /bin/bash -c "PATH=$PATH make -k check"</userinput></screen>
 
     <para>To receive a summary of the test suite results, run:</para>
@@ -127 +132 @@
     <para>A few unexpected failures cannot always be avoided. The GCC developers
     are usually aware of these issues, but have not resolved them yet.
-    In particular, six tests in the libstdc++ test suite are known to fail
-    when running as the root user as we do here.
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>