From: Michael Lippautz <michael.lippautz@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues with parallel build? (Was: gtk+native missing dep ?)
Date: Sat, 15 May 2010 10:35:48 +0200 [thread overview]
Message-ID: <1273912548.4196.2.camel@becca> (raw)
In-Reply-To: <1273859746.22943.454.camel@trini-m4400>
> On Fri, 2010-05-14 at 19:47 +0200, Andrea Adami wrote:
> > On Sat, May 8, 2010 at 1:12 PM, Andrea Adami <andrea.adami@gmail.com> wrote:
> > I repeated the build of console-image and gtk+-native always fails
> > using 4 threads.
> > Anyone can confirm?
Have seen such issues using 4 threads in other recipes too (can't
remember the names though)
Seems to be some race condition. (Using Angstrom, dunno if relevant)
Regards,
Michael
next prev parent reply other threads:[~2010-05-15 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 17:47 Issues with parallel build? (Was: gtk+native missing dep ?) Andrea Adami
2010-05-14 17:55 ` Tom Rini
2010-05-14 21:21 ` Andrea Adami
2010-05-15 0:04 ` Tom Rini
2010-05-16 18:52 ` Richard Purdie
2010-05-19 22:57 ` Andrea Adami
2010-06-08 15:33 ` Andrea Adami
2010-10-20 3:33 ` Denys Dmytriyenko
2010-05-15 8:35 ` Michael Lippautz [this message]
2010-05-15 15:52 ` Andrea Adami
2010-05-14 22:12 ` Leon Woestenberg
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=1273912548.4196.2.camel@becca \
--to=michael.lippautz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox