# HG changeset patch
# User Richard Strand <richard.strand@icomera.com>
# Date 1262976501 0
# Node ID 5d693a13c84abf6a00275dfb1413834056e000c0
# Parent  6f368c337f2d3f3f6f19fc88f6ed69a81d2956ef
documentation: Remove refs to seemingly native toolchains issue

Remove references to the seemingly native toolchains do not build
issue as it seems to be fixed.

Signed-off-by: Richard Strand <richard.strand@icomera.com>

diff -r 6f368c337f2d -r 5d693a13c84a docs/known-issues.txt
--- a/docs/known-issues.txt	Sat Jan 09 00:54:46 2010 +0100
+++ b/docs/known-issues.txt	Fri Jan 08 18:48:21 2010 +0000
@@ -32,32 +32,6 @@
 
 --------------------------------
 Symptoms:
-  Seemingly native toolchains do not build.
-
-Explanations:
-  Seemingly native toolchains are toolchains that target the same architecture
-  as the one it is built on, and on which it will run, but the machine tuple
-  may be different (eg i686 vs. i386, or x86_64-unknown-linux-gnu vs.
-  x86_64-pc-linux-gnu).
-
-  This seems to happen when building glibc-2.7 based toolchains only, for
-  x86 and for x86_64.
-
-  Only the system part of the tuple (here, linux-gnu) needs to be the same to
-  trigger the bug. Which means that building a tolchain for either x86 or
-  x86_64 on either x86 or x86_64 breaks.
-
-Fix:
-  None known.
-
-Workaround:
-  It seems that using -O2 in the CFLAGS fixes the problem. It has been
-  confirmed in the following threads:
-    http://sourceware.org/ml/crossgcc/2009-09/msg00055.html (for glibc)
-    http://sourceware.org/ml/crossgcc/2009-10/msg00001.html (for eglibc)
-
---------------------------------
-Symptoms:
   gcc is not found, although I *do* have gcc installed.
 
 Explanations:
diff -r 6f368c337f2d -r 5d693a13c84a docs/overview.txt
--- a/docs/overview.txt	Sat Jan 09 00:54:46 2010 +0100
+++ b/docs/overview.txt	Fri Jan 08 18:48:21 2010 +0000
@@ -626,20 +626,6 @@
     were all being hashed out, Canada had three national political parties.
     http://en.wikipedia.org/wiki/Cross_compiler
 
-Seemingly-native toolchains |
-----------------------------+
-
-Seemingly-native toolchains are toolchains that target the same architecture
-as the one it is built on, and on which it will run, but the machine tuple
-may be different (eg i686 vs. i386, or x86_64-unknown-linux-gnu vs.
-x86_64-pc-linux-gnu). This also applies if the target architecture is of the
-same kind (eg. x86 vs. x86_64, or ppc vs. ppc64).
-
-Such toolchain is tricky to build, as the configure scripts may incorrectly
-assume that files (headers and libs) from the build (or host) machine can be
-used by the cross-compiler it is going to build. The problem seems to arise
-only with glibc (and eglibc?) starting with version 2.7.
-
 
 ________________
                /