All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Can't build libcgroup
Date: Fri, 14 Oct 2011 17:55:56 +0200	[thread overview]
Message-ID: <j79m2c$ft4$1@dough.gmane.org> (raw)
In-Reply-To: <4E9858CF.2070902@mlbassoc.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 14-10-11 17:44, Gary Thomas schreef:
> On 2011-10-14 09:34, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Op 14-10-11 17:28, Khem Raj schreef:
>>>> Indeed, I did a rebuild from scratch with BB_NUMBER_THREADS=1 and 
>>>> PARALLEL_MAKE="-j1" and it worked fine.  When I set both to 2 I had
>>>> failures, but of a different sort (openssl failed to build).
>>>> 
>>>> Seems to be some real gremlins in the parallel builds :-(
>>>> 
>>>> Odd that I've never seen this when building Poky (I _always_ use 
>>>> BB_NUMBER_THREADS=4 and PARALLEL_MAKE="-j4")
>>>> 
>>> 
>>> It could be that the runqueue of poky is constructed such that this 
>>> does not happen
>> 
>> RP suspects it's rm_work that is triggering all these bitbake bugs.
> 
> Could well be - I'm convinced that rm_work is *evil* - it caused me no 
> end of woes in Poky, so I gave up on it.

If someone wants to sponsor larger SSDs for all angstrom developers we might
consider making rm_work opt-in :)

More seriously, bitbake needs to get fixed to work properly with rm_work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOmFuMMkyGM64RGpERAuikAKC2rXu0ekarJBbieRHPpye97NewSwCgoJZB
Smyl3Mh+U9RmQjGevwIfcfs=
=qJ0E
-----END PGP SIGNATURE-----




      reply	other threads:[~2011-10-14 16:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 13:39 Can't build libcgroup Gary Thomas
2011-10-13 14:16 ` Kridner, Jason
2011-10-13 14:28   ` Gary Thomas
2011-10-13 18:48     ` Khem Raj
2011-10-13 18:57       ` Gary Thomas
2011-10-13 20:33         ` Khem Raj
2011-10-13 20:42           ` Gary Thomas
2011-10-13 20:44             ` Khem Raj
2011-10-13 20:46               ` Gary Thomas
2011-10-13 20:58                 ` Andreas Müller
2011-10-13 21:12                   ` Gary Thomas
2011-10-14  4:37                     ` Jason Kridner
2011-10-14  5:17                       ` Khem Raj
2011-10-14 10:22                         ` Gary Thomas
2011-10-14 15:28                           ` Khem Raj
2011-10-14 15:34                             ` Koen Kooi
2011-10-14 15:44                               ` Gary Thomas
2011-10-14 15:55                                 ` Koen Kooi [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='j79m2c$ft4$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.