From 652d8eebd9e3b333954d67f8036df032c902493d Mon Sep 17 00:00:00 2001
From: Richard Strand <richard.strand@icomera.com>
Date: Fri, 8 Jan 2010 18:48:21 +0000
Subject: 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 --git a/docs/known-issues.txt b/docs/known-issues.txt
index 757939f..1b19bc1 100644
--- a/docs/known-issues.txt
+++ b/docs/known-issues.txt
@@ -32,32 +32,6 @@ So now, on for the real issues...
 
 --------------------------------
 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 --git a/docs/overview.txt b/docs/overview.txt
index 94c1f86..1a2a622 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -626,20 +626,6 @@ anyway!)
     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.
-
 
 ________________
                /
-- 
cgit v0.10.2-6-g49f6