On Wed, Mar 19, 2008 at 11:16 PM, Mike Frysinger
wrote:
> On Wed, Mar 19, 2008 at 6:15 PM, Bogdan Harjoc wrote:
> > You are perhaps referring to the variable that gentoo's portage [1]
> > accepts (and passes to ccache as an option).
>
> it was my understanding that ccache respected this. didnt
On Wed, Mar 19, 2008 at 6:15 PM, Bogdan Harjoc wrote:
> You are perhaps referring to the variable that gentoo's portage [1]
> accepts (and passes to ccache as an option).
it was my understanding that ccache respected this. didnt realize we
were hacking around the limitation in Gentoo by faking o
You are perhaps referring to the variable that gentoo's portage [1]
accepts (and passes to ccache as an option).
Explicitly not what I was looking for, but thanks.
Bogdan
[1]
http://sources.gentoo.org/viewcvs.py/portage/main/trunk/bin/ebuild.sh?view=markup
On Wed, Mar 19, 2008 at 9:57 PM, Mike F
On Wed, Mar 19, 2008 at 4:48 PM, Bogdan Harjoc wrote:
> Is the fact that the cache size limit is only configurable as a
> commandline option intentional ? There seem to be environment
> vars for virtually everything else but this.
use CCACHE_SIZE
-mike
Hello,
Is the fact that the cache size limit is only configurable as a
commandline option intentional ? There seem to be environment
vars for virtually everything else but this.
I am asking because I am close to the 1GB limit and it would be
tedious to change some build scripts to use CC='ccache
