From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: sstate status
Date: Wed, 8 Dec 2010 14:02:15 +0000 [thread overview]
Message-ID: <201012081402.16308.paul.eggleton@linux.intel.com> (raw)
On Wednesday 08 December 2010 11:41:22 you wrote:
> Do we still need those variable whitelisting changes? Based on original
> branch you pushed (basically RP's branch rebased on master imo), I think it
> basically works at least for a single recipe build though above weird issue
> exists for image build.
>
> Of course we need keep some bitbake specific variables in whitelist, such as
> DATE, TIME and several others you added in last commit.
Aren't many of those variables still exposed via preserved_envvars_list()?
> On the other hand, did you observe my issue on this new push? I want to
> understand its root cause, which is really funny.
I have to admit I didn't look closely enough to be sure - I was mainly testing between two different build machines which don't share the same native arch, so the native packages were rebuilt anyway. I'm starting a fresh build now with my new branch to see if I can reproduce your results.
Cheers,
Paul
next reply other threads:[~2010-12-08 14:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 14:02 Paul Eggleton [this message]
2010-12-08 14:06 ` sstate status Paul Eggleton
2010-12-08 14:15 ` Tian, Kevin
2010-12-08 14:50 ` Paul Eggleton
2010-12-08 14:52 ` Tian, Kevin
2010-12-08 14:41 ` Gary Thomas
2010-12-08 15:31 ` Gary Thomas
2010-12-08 15:55 ` Paul Eggleton
2010-12-08 17:14 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2010-12-03 16:34 Paul Eggleton
2010-12-03 22:11 ` Richard Purdie
2010-12-05 11:10 ` Tian, Kevin
2010-12-06 1:29 ` Richard Purdie
2010-12-07 7:46 ` Tian, Kevin
2010-12-07 15:02 ` Richard Purdie
2010-12-08 0:40 ` Tian, Kevin
2010-12-06 16:06 ` Paul Eggleton
2010-12-07 12:46 ` Richard Purdie
2010-12-07 16:36 ` Paul Eggleton
2010-12-08 11:22 ` Tian, Kevin
2010-12-08 11:31 ` Paul Eggleton
2010-12-08 11:41 ` Tian, Kevin
2010-12-03 23:31 ` Gary Thomas
2010-12-04 12:47 ` Gary Thomas
2010-12-05 11:19 ` Tian, Kevin
2010-12-05 12:02 ` Gary Thomas
2010-12-06 11:19 ` Gary Thomas
[not found] ` <4CFCC607.9040803@mlbassoc.com>
2010-12-07 7:17 ` Tian, Kevin
2010-12-05 11:07 ` Tian, Kevin
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=201012081402.16308.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=poky@pokylinux.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