From: Matt Madison <matt@madison.systems>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] image.bbclass: don't expand IMAGE_CMD when setting do_image task
Date: Wed, 27 Apr 2016 05:32:02 -0700 [thread overview]
Message-ID: <1461760323-27285-1-git-send-email-matt@madison.systems> (raw)
After being vexed with numerous taskhash mismatch errors on my
image builds, I think I hit on the source of the problem - the
value of the do_image_XXXX function reported by bitbake-dumpsig
had fully-expanded values for all of the variables referenced
in the function - so date and time stamps were showing up in
the text of the function.
Fixed this by not expanding the value of IMAGE_CMD during the
generation of the do_iamge_XXXX task. The vardeps still do
their job for detecting relevant changes.
Matt Madison (1):
image.bbclass: don't expand IMAGE_CMD when setting do_image task
meta/classes/image.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2016-04-27 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 12:32 Matt Madison [this message]
2016-04-27 12:32 ` [PATCH 1/1] image.bbclass: don't expand IMAGE_CMD when setting do_image task Matt Madison
2016-04-27 13:03 ` Richard Purdie
2016-04-27 14:19 ` Matt Madison
2016-04-27 14:39 ` Burton, Ross
2016-04-27 15:19 ` Matt Madison
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=1461760323-27285-1-git-send-email-matt@madison.systems \
--to=matt@madison.systems \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox