From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] pseudo: Fix problem related to realpath
Date: Fri, 10 Jun 2011 16:02:26 +0100 [thread overview]
Message-ID: <201106101602.27104.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <f4bf925e5ef24493da42015e1be93d59b85f3a44.1307639649.git.mark.hatle@windriver.com>
On Thursday 09 June 2011 18:15:45 Mark Hatle wrote:
> --- a/meta/recipes-devtools/pseudo/pseudo_1.1.1.bb
> +++ b/meta/recipes-devtools/pseudo/pseudo_1.1.1.bb
> @@ -1,9 +1,10 @@
> require pseudo.inc
>
> -PR = "r0"
> +PR = "r1"
I may be mistaken, but it seems to me that every time we need to rebuild
pseudo it results in a race when an older version of pseudo is present. We
handle building pseudo on its own first if it's not present, however if it just
needs updating we go ahead and rebuild it at the same time as building other
packages, and if it just happens that pseudo is needed when it's being built
-> bang. At least that's my assumption given that since the last batch of
updates, my rebuild of perl-native failed at the same time as pseudo's
do_compile with a large number of "ERROR: ld.so: object 'libpseudo.so' from
LD_PRELOAD cannot be preloaded: ignored" messages.
Am I right in that there's currently no mechanism to work around this?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-10 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 17:15 [PATCH 0/1] Fix realpath issue in pseudo Mark Hatle
2011-06-09 17:15 ` [PATCH 1/1] pseudo: Fix problem related to realpath Mark Hatle
2011-06-10 15:02 ` Paul Eggleton [this message]
2011-06-10 15:14 ` Mark Hatle
2011-06-10 15:19 ` Mark Hatle
2011-06-09 17:20 ` [PATCH 0/1] Fix realpath issue in pseudo Richard Purdie
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=201106101602.27104.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=mark.hatle@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