1.1 --- a/docs/known-issues.txt Fri Oct 02 22:10:38 2009 +0200
1.2 +++ b/docs/known-issues.txt Sun Jan 31 12:28:52 2010 +0100
1.3 @@ -32,32 +32,6 @@
1.4
1.5 --------------------------------
1.6 Symptoms:
1.7 - Seemingly native toolchains do not build.
1.8 -
1.9 -Explanations:
1.10 - Seemingly native toolchains are toolchains that target the same architecture
1.11 - as the one it is built on, and on which it will run, but the machine tuple
1.12 - may be different (eg i686 vs. i386, or x86_64-unknown-linux-gnu vs.
1.13 - x86_64-pc-linux-gnu).
1.14 -
1.15 - This seems to happen when building glibc-2.7 based toolchains only, for
1.16 - x86 and for x86_64.
1.17 -
1.18 - Only the system part of the tuple (here, linux-gnu) needs to be the same to
1.19 - trigger the bug. Which means that building a tolchain for either x86 or
1.20 - x86_64 on either x86 or x86_64 breaks.
1.21 -
1.22 -Fix:
1.23 - None known.
1.24 -
1.25 -Workaround:
1.26 - It seems that using -O2 in the CFLAGS fixes the problem. It has been
1.27 - confirmed in the following threads:
1.28 - http://sourceware.org/ml/crossgcc/2009-09/msg00055.html (for glibc)
1.29 - http://sourceware.org/ml/crossgcc/2009-10/msg00001.html (for eglibc)
1.30 -
1.31 ---------------------------------
1.32 -Symptoms:
1.33 gcc is not found, although I *do* have gcc installed.
1.34
1.35 Explanations: