path: root/docs
diff options
authorYann E. MORIN" <>2009-10-02 20:10:38 (GMT)
committerYann E. MORIN" <>2009-10-02 20:10:38 (GMT)
commit443f51a2dcaec99457e5797758c65e5c6c1d3664 (patch)
treebc547f4d8d24309bea92d91efd7ee42cffe4e427 /docs
parent7280facf183f25e49446588da64b4a0b8cf13ca6 (diff)
libc/glibc: fix building for seemingly native toolchains
Build glibc with -O2 as a fix/workaround to building seemingly-native toolchains. See: - docs/overview.txt - docs/known-issues.txt -
Diffstat (limited to 'docs')
2 files changed, 20 insertions, 2 deletions
diff --git a/docs/known-issues.txt b/docs/known-issues.txt
index 3c7eaab..757939f 100644
--- a/docs/known-issues.txt
+++ b/docs/known-issues.txt
@@ -51,8 +51,10 @@ Fix:
None known.
- If this happens for you, stick with glibc-2.6.1 for now.
- Or investigate! :-)
+ It seems that using -O2 in the CFLAGS fixes the problem. It has been
+ confirmed in the following threads:
+ (for glibc)
+ (for eglibc)
diff --git a/docs/overview.txt b/docs/overview.txt
index 3b100a1..8d9a6f0 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -28,6 +28,7 @@ Running crosstool-NG
Tools wrapper
Using the toolchain
Toolchain types
+ Seemingly-native toolchains
Makefile front-end
Kconfig parser
@@ -590,6 +591,21 @@ anyway!)
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.
Internals /