From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: why do numerous .bb files set "PARALLEL_MAKE"?
Date: Mon, 07 Nov 2011 10:22:26 +0000 [thread overview]
Message-ID: <1320661346.23708.9.camel@ted> (raw)
In-Reply-To: <20111104160759.GX9949@jama.jama.net>
On Fri, 2011-11-04 at 17:07 +0100, Martin Jansa wrote:
> On Fri, Nov 04, 2011 at 11:57:46AM -0400, Robert P. J. Day wrote:
> >
> > stumbled over this so i did a more thorough search:
> >
> > $ grep -w PARALLEL_MAKE $(find . -name *.bb)
> > ./meta/recipes-qt/qt-apps/qmmp_0.5.1.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-core/eggdbus/eggdbus_0.6.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-core/gettext/gettext_0.16.1.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-core/gettext/gettext_0.18.1.1.bb:#PARALLEL_MAKE = ""
> > ./meta/recipes-bsp/pciutils/pciutils_3.1.7.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-extended/sat-solver/sat-solver_git.bb:PARALLEL_MAKE=""
> > ./meta/recipes-extended/bash/bash_3.2.48.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-extended/tcp-wrappers/tcp-wrappers_7.6.bb:PARALLEL_MAKE = ""
> > ./meta/recipes-extended/groff/groff_1.20.1.bb:PARALLEL_MAKE = ""
> > ... more snipped ...
> >
> > why are individual recipes setting PARALLEL_MAKE to the empty
> > string? it's a *build* option, why would it have any relevance to
> > individual .bb files?
>
> because some projects fail to build in parallel and we don't have
> manpower to fix them all?
Just for reference we have actually fixed a lot of these in other
places, particularly where they're on the critical path. The situation
is a lot better than it ever used to be although obviously still room
for improvement!
Cheers,
Richard
prev parent reply other threads:[~2011-11-07 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 15:57 why do numerous .bb files set "PARALLEL_MAKE"? Robert P. J. Day
2011-11-04 16:03 ` Joshua Lock
2011-11-04 16:06 ` Robert P. J. Day
2011-11-04 16:10 ` Chris Larson
2011-11-04 16:05 ` Gary Thomas
2011-11-04 16:07 ` Martin Jansa
2011-11-04 16:12 ` Robert P. J. Day
2011-11-07 10:22 ` Richard Purdie [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=1320661346.23708.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=yocto@yoctoproject.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.