[PATCH 1 of 1] documentation: Remove refs to seemingly native toolchains issue
Fri Jan 8 18:57:00 GMT 2010
# HG changeset patch
# User Richard Strand <email@example.com>
# Date 1262976501 0
# Node ID cf33d0e2af4b66dc50f2057f2c933946288fb515
# Parent 6df0d71a7a55dc702b26aae3397b0344f9b9805c
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 <firstname.lastname@example.org>
diff -r 6df0d71a7a55 -r cf33d0e2af4b docs/known-issues.txt
--- a/docs/known-issues.txt Thu Jan 07 23:05:30 2010 +0100
+++ b/docs/known-issues.txt Fri Jan 08 18:48:21 2010 +0000
@@ -32,32 +32,6 @@
- Seemingly native toolchains do not build.
- 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.
- 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.
- None known.
- 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)
gcc is not found, although I *do* have gcc installed.
diff -r 6df0d71a7a55 -r cf33d0e2af4b docs/overview.txt
--- a/docs/overview.txt Thu Jan 07 23:05:30 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.
-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.
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc