From: Bob Cochran <yocto@mindchasers.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: ccache
Date: Tue, 10 Apr 2012 20:51:53 -0400 [thread overview]
Message-ID: <4F84D5A9.3080509@mindchasers.com> (raw)
In-Reply-To: <CABcZANkiFDcOdLfJy5y0OZTkQzUEaC3ip_CF84iZKp6MV3aZYQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-04-11 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 17:31 ccache Gary Thomas
2012-04-03 17:36 ` ccache Chris Larson
2012-04-11 0:51 ` Bob Cochran [this message]
2012-04-11 12:20 ` ccache Richard Purdie
2012-04-05 1:45 ` ccache Ni Qingliang
2012-04-12 9:03 ` ccache Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F84D5A9.3080509@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=clarson@kergoth.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.