diff options
author | Richard Strand <richard.strand@icomera.com> | 2010-01-08 18:48:21 (GMT) |
---|---|---|
committer | Richard Strand <richard.strand@icomera.com> | 2010-01-08 18:48:21 (GMT) |
commit | 652d8eebd9e3b333954d67f8036df032c902493d (patch) | |
tree | 546fb8d1331ea42cb7bbc5bc9faab936368551d3 /docs/known-issues.txt | |
parent | 55423f206fbce32b166778ec4932178be4a43c23 (diff) |
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>
Diffstat (limited to 'docs/known-issues.txt')
-rw-r--r-- | docs/known-issues.txt | 26 |
1 files changed, 0 insertions, 26 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: |