Hi,
Adam Stirk wrote:
Hi,
Is there a reason why when compiling GCC compiler cache is not used?
If I would like to test it where would I need to start looking?
Thanks
Adam
In theory it should indeed just work. We disabled ccache during gcc
explicitly,
because we experienced some rather hard to track cache miss-use building
multilib gcc variants (those supporting more than one target architecture,
such as i386/x86-64, ppc(32)/ppc64, or sparc(32)/sparc64 at a time).
If you want to investigate this, remove the conditional from:
package/develop/ccache/parse-config
if [ "$pkg" == gcc -a "$SDECFG_MULTILIB" = 1 ]; then
: # in GCC multilib builds the ccache hash currently collides
(or so)
...
And give it a spin with a fresh x86-64 build, if you are lucky it
even just works these days :-)
PS: "svn blame" and "svn log" are usually a great help to get an idea
why some specific code is there.
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
