|
|
@@ -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 \&\& \!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>
|
|
|
|
Krejzi