From: Kevin Tian <kevin.tian@intel.com>
To: poky@pokylinux.org
Subject: [PATCH 0/1] fix broken sstate in fork() model
Date: Tue, 21 Dec 2010 15:07:33 +0800 [thread overview]
Message-ID: <849307$arkaj1@azsmga001.ch.intel.com> (raw)
Frankly speaking I'm not very clear about which part of data requires re-initialization
and which part doesn't in the child. But one obvious difference from previous exec()
model is that environmental variables are not exported again since they're already in
the data store. Original way to pass BB_TASKHASH through env now simply breaks and thus
there's no signature in sstate packages. The fix is simple, to simply set variable
directly, but I'm not sure whether there're other similar issues regarding to env handle
here...
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: tk/master
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tk/master
Thanks,
Kevin Tian <kevin.tian@intel.com>
---
Kevin Tian (1):
runqueue.py: set BB_TASKHASH approriately after moving to fork()
bitbake/lib/bb/runqueue.py | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
reply other threads:[~2010-12-21 7:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='849307$arkaj1@azsmga001.ch.intel.com' \
--to=kevin.tian@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