Re: CCache
Thanks, do I bug you that much you actually remember what architecture I'm running? LOL (René said "And
give it a spin with a fresh x86-64 build" and I didn't even mention my architecture :) )
I hope the compiler cache works it might speed up my build time as GCC takes an age to compile as probably
everyone knows.
I did try "svn diff" when you suggested it but I couldn't get it to work. I shall try the 2 new commands when I get
a chance, as I like trying new things. I'm still a newbie when it come to Linux but I think I'm managing ok so
far, working in IT and having some programming background helps.
I will bash out a few patches (openntpd, php and linux-igd(new)) this evening after installing my latest build.
Thanks
Adam
-----Original Message-----
From: René Rebe
Sent: 11 August 2008 17:09
To: Adam Stirk
Cc: T2 developers mailing list
Subject: Re: [t2] CCache
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
Thanks, do I bug you that much you actually remember what architecture I'm running? LOL (René said "And
give it a spin with a fresh x86-64 build" and I didn't even mention my architecture :) )
I hope the compiler cache works it might speed up my build time as GCC takes an age to compile as probably
everyone knows.
I did try "svn diff" when you suggested it but I couldn't get it to work. I shall try the 2 new commands when I get
a chance, as I like trying new things. I'm still a newbie when it come to Linux but I think I'm managing ok so
far, working in IT and having some programming background helps.
I will bash out a few patches (openntpd, php and linux-igd(new)) this evening after installing my latest build.
Thanks
Adam
-----Original Message-----
From: René Rebe
Sent: 11 August 2008 17:09
To: Adam Stirk
Cc: T2 developers mailing list
Subject: Re: [t2] CCache
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
RSS Feed