summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/known-issues.txt26
-rw-r--r--docs/overview.txt14
2 files changed, 0 insertions, 40 deletions
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.
-
________________
/