* ccache
@ 2012-04-03 17:31 Gary Thomas
2012-04-03 17:36 ` ccache Chris Larson
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Gary Thomas @ 2012-04-03 17:31 UTC (permalink / raw)
To: Poky Project
Why is ccache being used for Poky/Yocto builds? My understanding is
that it's a win for _rebuilds_ of the same/related files, but there's
not a whole lot of that going on.
If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
which is 1.8GB - quite a bite! Is there some way to disable this?, other
than not have ccache on my host computer (not an option as it is useful
for other builds I do)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ccache
2012-04-03 17:31 ccache Gary Thomas
@ 2012-04-03 17:36 ` Chris Larson
2012-04-11 0:51 ` ccache Bob Cochran
2012-04-05 1:45 ` ccache Ni Qingliang
2012-04-12 9:03 ` ccache Richard Purdie
2 siblings, 1 reply; 6+ messages in thread
From: Chris Larson @ 2012-04-03 17:36 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
On Tue, Apr 3, 2012 at 10:31 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> Why is ccache being used for Poky/Yocto builds? My understanding is
> that it's a win for _rebuilds_ of the same/related files, but there's
> not a whole lot of that going on.
>
> If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
> which is 1.8GB - quite a bite! Is there some way to disable this?, other
> than not have ccache on my host computer (not an option as it is useful
> for other builds I do)
I think the default behavior of using ccache when it's installed is
extremely bad, and dangerous, in that the ccache object cache is of
both limited usefulness, as you say, and the object cache can get
corrupted, leading to extremely odd behavior (and it's rarely a place
you think to look as a cause). At Mentor we disabled this behavior,
and I really, really think we should do so in the default oe-core
bitbake.conf.
--
Christopher Larson
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ccache
2012-04-03 17:31 ccache Gary Thomas
2012-04-03 17:36 ` ccache Chris Larson
@ 2012-04-05 1:45 ` Ni Qingliang
2012-04-12 9:03 ` ccache Richard Purdie
2 siblings, 0 replies; 6+ messages in thread
From: Ni Qingliang @ 2012-04-05 1:45 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
On Wed, 2012-04-04 at 01:31 +0800, Gary Thomas wrote:
> Why is ccache being used for Poky/Yocto builds? My understanding is
> that it's a win for _rebuilds_ of the same/related files, but there's
> not a whole lot of that going on.
>
> If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
> which is 1.8GB - quite a bite! Is there some way to disable this?, other
> than not have ccache on my host computer (not an option as it is useful
> for other builds I do)
>
I add following line in the 'local.conf':
CCACHE=""
--
Yi Qingliang
niqingliang@insigma.com.cn
https://niqingliang2003.wordpress.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ccache
2012-04-03 17:36 ` ccache Chris Larson
@ 2012-04-11 0:51 ` Bob Cochran
2012-04-11 12:20 ` ccache Richard Purdie
0 siblings, 1 reply; 6+ messages in thread
From: Bob Cochran @ 2012-04-11 0:51 UTC (permalink / raw)
To: Chris Larson; +Cc: Poky Project
On 04/03/2012 01:36 PM, Chris Larson wrote:
> On Tue, Apr 3, 2012 at 10:31 AM, Gary Thomas<gary@mlbassoc.com> wrote:
>> Why is ccache being used for Poky/Yocto builds? My understanding is
>> that it's a win for _rebuilds_ of the same/related files, but there's
>> not a whole lot of that going on.
>>
>> If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
>> which is 1.8GB - quite a bite! Is there some way to disable this?, other
>> than not have ccache on my host computer (not an option as it is useful
>> for other builds I do)
>
> I think the default behavior of using ccache when it's installed is
> extremely bad, and dangerous, in that the ccache object cache is of
> both limited usefulness, as you say, and the object cache can get
> corrupted, leading to extremely odd behavior (and it's rarely a place
> you think to look as a cause). At Mentor we disabled this behavior,
> and I really, really think we should do so in the default oe-core
> bitbake.conf.
It would be nice / cleaner to not build out the hollow ccache directory
structure under tmp when ccache isn't installed or being used. Seeing
it there under tmp with levels of empty sub directories beneath it is
somewhat confusing.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ccache
2012-04-11 0:51 ` ccache Bob Cochran
@ 2012-04-11 12:20 ` Richard Purdie
0 siblings, 0 replies; 6+ messages in thread
From: Richard Purdie @ 2012-04-11 12:20 UTC (permalink / raw)
To: Bob Cochran; +Cc: Chris Larson, Poky Project
On Tue, 2012-04-10 at 20:51 -0400, Bob Cochran wrote:
> On 04/03/2012 01:36 PM, Chris Larson wrote:
> > On Tue, Apr 3, 2012 at 10:31 AM, Gary Thomas<gary@mlbassoc.com> wrote:
> >> Why is ccache being used for Poky/Yocto builds? My understanding is
> >> that it's a win for _rebuilds_ of the same/related files, but there's
> >> not a whole lot of that going on.
> >>
> >> If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
> >> which is 1.8GB - quite a bite! Is there some way to disable this?, other
> >> than not have ccache on my host computer (not an option as it is useful
> >> for other builds I do)
> >
> > I think the default behavior of using ccache when it's installed is
> > extremely bad, and dangerous, in that the ccache object cache is of
> > both limited usefulness, as you say, and the object cache can get
> > corrupted, leading to extremely odd behavior (and it's rarely a place
> > you think to look as a cause). At Mentor we disabled this behavior,
> > and I really, really think we should do so in the default oe-core
> > bitbake.conf.
>
>
> It would be nice / cleaner to not build out the hollow ccache directory
> structure under tmp when ccache isn't installed or being used. Seeing
> it there under tmp with levels of empty sub directories beneath it is
> somewhat confusing.
I'm tempted to move all the ccache stuff into a separate class and then
drop the inherit by default.
Patches welcome for 1.3...
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ccache
2012-04-03 17:31 ccache Gary Thomas
2012-04-03 17:36 ` ccache Chris Larson
2012-04-05 1:45 ` ccache Ni Qingliang
@ 2012-04-12 9:03 ` Richard Purdie
2 siblings, 0 replies; 6+ messages in thread
From: Richard Purdie @ 2012-04-12 9:03 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
On Tue, 2012-04-03 at 11:31 -0600, Gary Thomas wrote:
> Why is ccache being used for Poky/Yocto builds? My understanding is
> that it's a win for _rebuilds_ of the same/related files, but there's
> not a whole lot of that going on.
>
> If I build core-image-sato from scratch, I end up with ${BUILD}/tmp/ccache
> which is 1.8GB - quite a bite! Is there some way to disable this?,
CCACHE = ""
in a conf file.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-04-12 9:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-03 17:31 ccache Gary Thomas
2012-04-03 17:36 ` ccache Chris Larson
2012-04-11 0:51 ` ccache Bob Cochran
2012-04-11 12:20 ` ccache Richard Purdie
2012-04-05 1:45 ` ccache Ni Qingliang
2012-04-12 9:03 ` ccache Richard Purdie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.