aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/gcc.xml
diff options
context:
space:
mode:
authorBruce Dubbs <bdubbs@linuxfromscratch.org>2015-04-24 21:19:59 +0000
committerBruce Dubbs <bdubbs@linuxfromscratch.org>2015-04-24 21:19:59 +0000
commit0238d4951e3fb765ad71e98fd467b9a555bd3f7e (patch)
tree68356fa0220a0e1b65eef0104ddc65ee930b122f /chapter06/gcc.xml
parent320fdc6eacad12efafdaf03d78a5dffe6fdcd131 (diff)
Update known regression test failures for gcc and glibc.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10906 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/gcc.xml')
-rw-r--r--chapter06/gcc.xml16
1 files changed, 2 insertions, 14 deletions
diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml
index ab0fde85a..7616b30ac 100644
--- a/chapter06/gcc.xml
+++ b/chapter06/gcc.xml
@@ -40,17 +40,7 @@
<sect2 role="installation">
<title>Installation of GCC</title>
-<!--
- <para>As in Chapter 5, fix a problem identified upstream:</para>
-<screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&amp;\&amp; \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen>
-
-
- <para>Now fix another problem identified upstream that causes some
- programs to fail:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-patch;</userinput></screen>
--->
<para>The GCC documentation recommends building GCC outside of the source
directory in a dedicated build directory:</para>
@@ -121,10 +111,8 @@ cd ../gcc-build</userinput></screen>
url="&test-results;"/> and <ulink url="http://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
<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, the <filename class="libraryfile">libmudflap</filename> tests
- are known to be particularly problematic as a result of a bug in GCC
- (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>). -->
+ are usually aware of these issues, but have not resolved them yet.
+ In particular, four tests in the libgomp test suite are known to fail.
Unless the test results are vastly different from those at the above URL,
it is safe to continue.</para>