From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Issue with pseudo on 64-bit build host
Date: Wed, 26 Jun 2013 12:43:50 -0500 [thread overview]
Message-ID: <20130626124350.4d054ea7@e6410-2> (raw)
In-Reply-To: <CA+AhUGyTo0i4Qq5gScLXs3c_CAs16xnozi0JkteRiq_qS6R1Qg@mail.gmail.com>
On Wed, 26 Jun 2013 19:05:05 +0200
Erik Botö <erik.boto@pelagicore.com> wrote:
> Yes PSEUDO_UNLOAD=1 should do that, but the hosts libpseudo is not
> found when invoking qemu. Therefore the code in pseudo that would
> clean the environment of any libpseudo.so in LD_PRELOAD before handing
> of to qemu is not run and LD_PRELOAD still contains libpseudo.so in
> the qemu environment.
Hmm. I'm wondering what the order of operations in the shell is. In theory,
nearly all of bitbake should be running with libpseudo loaded, just often in
PSEUDO_DISABLED mode. I wonder whether maybe there's some shells that set
the environment variable up, then fork, and some that fork, then set the
environment variable. That could do it. Pseudo will check the environment
variable on both fork and exec, I believe. But if we are able to end up
getting into a situation where libpseudo.so is in LD_PRELOAD, but doesn't
get found, then yeah, PSEUDO_UNLOAD won't work.
And yes, it should be lib64, not lib, I think.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2013-06-26 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 9:33 Issue with pseudo on 64-bit build host Erik Botö
2013-06-26 13:30 ` Laurentiu Palcu
2013-06-26 17:05 ` Erik Botö
2013-06-26 17:43 ` 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=20130626124350.4d054ea7@e6410-2 \
--to=peter.seebach@windriver.com \
--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