All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Simultaneous build of two intree packages
Date: Mon, 07 May 2012 06:02:39 -0600	[thread overview]
Message-ID: <4FA7B9DF.60304@mlbassoc.com> (raw)
In-Reply-To: <1336391680.3417.7.camel@dasty-laptop>

On 2012-05-07 05:54, Radek Dostal wrote:
> Dear All,
>
> I have three intree recipes A, B and C which are part of the same layer.
> =>  B depends on A
> =>  C depends on A.
>
> There is no dependency between B and C. Only important thing is that B
> and C are not build simultaneously. This is not a problem unless I use
> configure BB_NUMBER_THREADS>  1. Than builds B and C starts to collide
> and produce mess because they are both intree builds.

What are you doing that makes these clash?

>
> Is there something like a mutex/lock mechanism in openembedded-core,
> which would forbid two recipes to be build simultaneously?

Just make C depend on B

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



  reply	other threads:[~2012-05-07 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 11:54 Simultaneous build of two intree packages Radek Dostal
2012-05-07 12:02 ` Gary Thomas [this message]
2012-05-07 12:33   ` Radek Dostal
2012-05-07 15:46     ` Khem Raj
2012-05-07 21:01       ` Radek Dostal
2012-05-07 21:08         ` Gary Thomas
2012-05-07 21:23           ` Radek Dostal
2012-05-08 23:36             ` Ciprian Ciubotariu
2012-05-07 21:42         ` Khem Raj
2012-05-07 21:42         ` Khem Raj
2012-05-08 21:31     ` Ulf Samuelsson
2012-05-09  7:27       ` Radek Dostal

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=4FA7B9DF.60304@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-devel@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 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.