From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: paul.eggleton@linux.intel.com, gratian.crisan@ni.com,
ken.sharp@ni.com, openembedded-core@lists.openembedded.org
Subject: Re: [dylan, master][PATCH] autotools.bbclass: Fix race with sed-native
Date: Sat, 05 Oct 2013 08:37:00 +0100 [thread overview]
Message-ID: <1380958620.30971.9.camel@ted> (raw)
In-Reply-To: <524F85EA.30805@linux.intel.com>
On Fri, 2013-10-04 at 20:22 -0700, Saul Wold wrote:
> On 10/04/2013 04:35 PM, Richard Tollerton wrote:
> > Suppose the following:
> > 1) foo.do_configure/do_build runs in parallel with
> > sed-native.do_configure;
> > 2) foo.do_configure/do_build makes use of sed (i.e. inherits autotools);
> > 3) A previously built sed-native already exists in the native sysroot,
> > and in the sstate cache.
> >
> > Then sed-native may be deleted from its sysroot via
> > sstate_clean_manifest while foo.do_configure/do_build is using it,
> > leading to an irreproducible build failure.
> >
> > This fix does for sed-native what's already done for libtool-native,
> > with some additional light refactoring.
> >
> This also starts to create more front end bottle next on autotools
> related items before we can really start to parallelize the build.
>
> More thought is required on this.
Please have a look at the sed-native changes that went into master
recently as I think this issue has been fixed differently...
Cheers,
Richard
next prev parent reply other threads:[~2013-10-05 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 23:35 [dylan, master][PATCH] autotools.bbclass: Fix race with sed-native Richard Tollerton
2013-10-05 3:22 ` Saul Wold
2013-10-05 7:37 ` Richard Purdie [this message]
2013-10-08 2:44 ` Richard Tollerton
2013-10-08 12:19 ` Richard Purdie
2013-10-08 13:03 ` Enrico Scholz
2013-10-08 17:47 ` Richard Tollerton
2013-10-10 9:00 ` Richard Purdie
2013-10-10 10:29 ` Phil Blundell
2013-10-08 2:55 ` Richard Tollerton
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=1380958620.30971.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gratian.crisan@ni.com \
--cc=ken.sharp@ni.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=sgw@linux.intel.com \
/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.