From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] ccache: set COMPILERCHECK to 'none'
Date: Thu, 08 Mar 2012 22:57:21 +0100 [thread overview]
Message-ID: <8762eeeoxq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <351a3eaf5539eda4c54d1f9eb655d3e4d8b9654c.1331148403.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 7 Mar 2012 20:26:50 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> This allows ccache to re-use its cache contents even if the compiler
Thomas> binary mtime has changed. It is the simplest approach to solve this
Thomas> problem, and it works for the internal, external and crosstool-ng
Thomas> toolchain backends.
Thomas> Of course, it leaves the user responsible for invalidating the cache
Thomas> when necessary, but there doesn't seem to be a real good solution that
Thomas> allows both to: 1/ keep the cache contents accross builds and re-use
Thomas> it and 2/ invalidate the cache automatically when the compiler chances
Thomas> in an incompatible way.
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-03-08 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 19:26 [Buildroot] [pull request] Pull request for branch for-2012.05/ccache-fixes Thomas Petazzoni
2012-03-07 19:26 ` [Buildroot] [PATCH 1/2] ccache: Force ccache to use its internal zlib Thomas Petazzoni
2012-03-08 21:57 ` Peter Korsgaard
2012-03-07 19:26 ` [Buildroot] [PATCH 2/2] ccache: set COMPILERCHECK to 'none' Thomas Petazzoni
2012-03-08 21:57 ` Peter Korsgaard [this message]
2012-03-10 11:39 ` Arnout Vandecappelle
2012-03-07 19:40 ` [Buildroot] [pull request] Pull request for branch for-2012.05/ccache-fixes Thomas Petazzoni
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=8762eeeoxq.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox