From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: What's this
Date: Tue, 7 Jun 2016 18:58:37 +0200 [thread overview]
Message-ID: <5756FD3D.3010109@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0La74HkwkgqQZwECS2ruzSe-guCCBJFG0_u=e1FBT8q3CA@mail.gmail.com>
On 2016-06-07 18:20, Burton, Ross wrote:
>
> On 7 June 2016 at 17:02, Burton, Ross <ross.burton@intel.com <mailto:ross.burton@intel.com>> wrote:
>
> It means the hash calculated my the bitbake master was different to the hash calculated when the worker started up.
> This usually means that you're using something like ${TIME} in the recipe but not marking it appropriatly so the
> cache ignores it. Do you have a base-files bbappend that writes a timestamp?
>
>
> The always wise Joshua reminds me that if your DISTRO_VERSION contains ${DATETIME} then this happens. If you're doing
> this then you'll want to set [vardepsexclude] on DISTRO_VERSION to stop the DATETIME from getting into the cache (or not
> put the current date/time into the distro version).
>
Ah, that's probably it. Exactly how do I set that exclusion?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-06-07 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 16:44 What's this Gary Thomas
2016-06-07 16:02 ` Burton, Ross
2016-06-07 16:20 ` Burton, Ross
2016-06-07 16:58 ` Gary Thomas [this message]
2016-06-07 21:29 ` Joshua G Lock
2016-06-07 21:24 ` Paul Eggleton
2016-06-07 22:20 ` Richard Purdie
2016-06-08 8:59 ` Paul Eggleton
2016-06-08 11:30 ` Richard Purdie
2016-06-08 9:08 ` Mike Looijmans
2016-06-08 9:18 ` Gary Thomas
2016-06-08 11:59 ` Julien Gueytat
2016-06-07 16:24 ` Gary Thomas
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=5756FD3D.3010109@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ross.burton@intel.com \
--cc=yocto@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.