1.1 --- a/docs/known-issues.txt Fri Aug 08 07:07:16 2008 +0000
1.2 +++ b/docs/known-issues.txt Sun Oct 26 11:26:46 2008 +0000
1.3 @@ -44,10 +44,8 @@
1.4 x86 and for x86_64.
1.5
1.6 Only the system part of the tuple (here, linux-gnu) needs to be the same to
1.7 - trigger the bug.
1.8 -
1.9 - If you really cross-compile (eg x86 -> x86_64, or the other way around),
1.10 - the toolchain builds successfully.
1.11 + trigger the bug. Which means that building a tolchain for either x86 or
1.12 + x86_64 on either x86 or x86_64 breaks.
1.13
1.14 Fix:
1.15 None known.
1.16 @@ -57,3 +55,22 @@
1.17 Or investigate! :-)
1.18
1.19 --------------------------------
1.20 +Symptoms:
1.21 + gcc is not found, although I *do* have gcc installed.
1.22 +
1.23 +Explanations:
1.24 + This is an issue on at least RHEL systems, where gcc is a symlink to ccache.
1.25 + Because crosstool-NG create links to gcc for the build and host environment,
1.26 + those symlinks are in fact pointing to ccache, which then doesn't know how
1.27 + to run the compiler.
1.28 +
1.29 + A possible fix could probably set the environment variable CCACHE_CC to the
1.30 + actual compiler used.
1.31 +
1.32 +Fix:
1.33 + None known.
1.34 +
1.35 +Workaround:
1.36 + Uninstall ccache.
1.37 +
1.38 +--------------------------------