From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: pseudo interaction issue
Date: Mon, 26 Mar 2012 15:41:37 -0500 [thread overview]
Message-ID: <20120326154137.4e613c70@wrlaptop> (raw)
In-Reply-To: <1332609315.28414.19.camel@ted>
Oh, nevermind, I just realized: We use antimagic as the implementation
goo for PSEUDO_DISABLED.
So a call to os.popen() from a program which has PSEUDO_DISABLED set is
going to think it's in antimagic mode.
And suddenly, the trick is revealed:
os.popen() is bypassing all the runqueue stuff which is trying to
ensure that the environment is in a valid state. So if bitbake code
calls os.popen(), it may behave weirdly, for the same reason that any
other direct invocation of fork() or system() or whatnot would behave
weirdly -- because bitbake is running with pseudo in a strange state.
So I think the thing is:
Because bitbake is running with PSEUDO_DISABLED, any child process that
is not explicitly set to either enable or unload pseudo is going to be
running under pseudo, with PSEUDO_DISABLED. And that means we need to
ensure that PSEUDO_PREFIX stays set, because we need that even when
pseudo is disabled. (It's used during some of the initial setup
sanity checks.)
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2012-03-26 20:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 17:35 pseudo interaction issue Paul Eggleton
2012-02-17 18:50 ` Mark Hatle
2012-03-14 9:02 ` Xu, Dongxiao
2012-03-22 1:49 ` Xu, Dongxiao
2012-03-22 16:18 ` Peter Seebach
2012-03-23 1:01 ` Xu, Dongxiao
2012-03-23 2:29 ` Peter Seebach
2012-03-23 3:21 ` Xu, Dongxiao
2012-03-23 7:16 ` Peter Seebach
2012-03-23 12:20 ` Paul Eggleton
2012-03-23 20:06 ` Peter Seebach
2012-03-23 22:45 ` Peter Seebach
2012-03-24 17:15 ` Richard Purdie
2012-03-24 17:41 ` Richard Purdie
2012-03-26 16:44 ` Peter Seebach
2012-03-26 16:47 ` Richard Purdie
2012-03-26 17:18 ` Peter Seebach
2012-03-26 21:45 ` Richard Purdie
2012-03-27 3:47 ` Peter Seebach
2012-03-27 14:26 ` Peter Seebach
2012-03-26 7:43 ` Peter Seebach
2012-03-26 9:23 ` Richard Purdie
2012-03-26 20:36 ` Peter Seebach
2012-03-26 20:41 ` Peter Seebach [this message]
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=20120326154137.4e613c70@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--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.