diff options
| author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2018-08-12 16:35:49 +0000 |
|---|---|---|
| committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2018-08-12 16:35:49 +0000 |
| commit | 76db8d6fa13e6c7c133fc1118c127bce9dcb8564 (patch) | |
| tree | 66e0c62c6ff448dcc6f3311b890d354b913de00e /chapter06/gcc.xml | |
| parent | 059c79e4530a1c91ae18d0bdf77c366f40911676 (diff) | |
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
Diffstat (limited to 'chapter06/gcc.xml')
| -rw-r--r-- | chapter06/gcc.xml | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index 645b72cfa..c1a074911 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -109,9 +109,14 @@ cd build</userinput></screen> <screen><userinput remap="test">ulimit -s 32768</userinput></screen> - <para>Test the results, but do not stop at errors:</para> + <para>Remove one test known to cause a problem:</para> -<screen><userinput remap="test">make -k check</userinput></screen> +<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> @@ -126,8 +131,6 @@ cd build</userinput></screen> <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> |