Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/ccache: add wrapper for internal toolchain
Date: Sun, 26 Apr 2015 11:37:42 +0200	[thread overview]
Message-ID: <20150426113742.182fa26b@free-electrons.com> (raw)
In-Reply-To: <1430040062-46308-2-git-send-email-kaszak@gmail.com>

Dear Karoly Kasza,

On Sun, 26 Apr 2015 11:21:02 +0200, Karoly Kasza wrote:
> This patch will make ccache to use mtime for compiler checks except for
> BR's internal toolchain, where using mtime would make ccache useless,
> because of the recompilations of the binaries. In this case we use
> a wrapper script and an md5 hash file with the BR .config options as
> suggested previously by Arnout.

Well, even for external toolchains using the mtime on the compiler in
$(HOST_DIR)/usr/bin will not work. Because the compiler in
$(HOST_DIR)/usr/bin is not actually the compiler, but a binary wrapper
built by Buildroot, for which the mtime will change at each build.

I must say I don't quite like the fact that the solution used here is
different between internal and external toolchain, but I haven't
thought too much of the problem.

How would ccache work with external toolchains?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-26  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26  9:21 [Buildroot] [PATCH 1/2] package/ccache: bump to version 3.2.1 Karoly Kasza
2015-04-26  9:21 ` [Buildroot] [PATCH 2/2] package/ccache: add wrapper for internal toolchain Karoly Kasza
2015-04-26  9:37   ` Thomas Petazzoni [this message]
2015-04-26  9:45     ` Károly Kasza
2015-04-26 12:24       ` Thomas Petazzoni
2015-04-26 12:34         ` Károly Kasza
2015-04-27  8:10           ` Károly Kasza
2015-04-26  9:27 ` [Buildroot] [PATCH 1/2] package/ccache: bump to version 3.2.1 Baruch Siach
2015-04-26  9:38   ` Károly Kasza
2015-04-26  9:41     ` Baruch Siach

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=20150426113742.182fa26b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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