From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: why do numerous .bb files set "PARALLEL_MAKE"?
Date: Fri, 04 Nov 2011 09:03:56 -0700 [thread overview]
Message-ID: <4EB40CEC.4030106@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1111041153170.6678@localhost6.localdomain6>
On 04/11/11 08:57, 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 that individual BB file has problems being run with parallel
make (make -j).
>
> conversely, i don't see a single .bb file that sets
> BB_NUMBER_THREADS. the above just looks ... odd.
That's the amount of threads BitBake creates, tasks it will run in parallel.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-04 16:04 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 [this message]
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
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=4EB40CEC.4030106@linux.intel.com \
--to=josh@linux.intel.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.