path: root/docs
diff options
authorYann E. MORIN" <>2008-09-28 21:35:44 (GMT)
committerYann E. MORIN" <>2008-09-28 21:35:44 (GMT)
commit8cf6201cbd117d52fca3c129a17739a8fbb1bc59 (patch)
treeb02843476c812f64c40033cec5899ccac67394f6 /docs
parentb000bc94cd37d3f41e9e0144c02b4cfe4066a351 (diff)
Had a new known issue: ccache will break the build because we're sym-linking to have our own compiler for host and build systems, but that screws up ccache finding the real compiler.
There is no fix, so the only way to inform the users is to document it: remove ccache. /trunk/docs/known-issues.txt | 25 21 4 0 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-)
Diffstat (limited to 'docs')
1 files changed, 21 insertions, 4 deletions
diff --git a/docs/known-issues.txt b/docs/known-issues.txt
index 5228b10..b318de3 100644
--- a/docs/known-issues.txt
+++ b/docs/known-issues.txt
@@ -44,10 +44,8 @@ Explanations:
x86 and for x86_64.
Only the system part of the tuple (here, linux-gnu) needs to be the same to
- trigger the bug.
- If you really cross-compile (eg x86 -> x86_64, or the other way around),
- the toolchain builds successfully.
+ trigger the bug. Which means that building a tolchain for either x86 or
+ x86_64 on either x86 or x86_64 breaks.
None known.
@@ -57,3 +55,22 @@ Workaround:
Or investigate! :-)
+ gcc is not found, although I *do* have gcc installed.
+ This is an issue on at least RHEL systems, where gcc is a symlink to ccache.
+ Because crosstool-NG create links to gcc for the build and host environment,
+ those symlinks are in fact pointing to ccache, which then doesn't know how
+ to run the compiler.
+ A possible fix could probably set the environment variable CCACHE_CC to the
+ actual compiler used.
+ None known.
+ Uninstall ccache.