From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] packages: fix and improve support for top-level parallel makefile
Date: Tue, 21 Apr 2015 22:00:34 +0200 [thread overview]
Message-ID: <5536AC62.3020702@mind.be> (raw)
In-Reply-To: <CAHkwnC88R9T-01ZQvscus7MwHop3u3i1iavHwJXXcUT42rJ7Fg@mail.gmail.com>
Thanks for your explanation, I see now why my alternative won't work.
On 21/04/15 05:01, Fabio Porcedda wrote:
> On Mon, Apr 20, 2015 at 11:35 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 06/04/15 15:50, Fabio Porcedda wrote:
>>> To fix packages that fail to build when PARALLEL_JOBS is empty instead
>>> of using an empty PARALLEL_JOBS just avoid to using it in
>>> the MAKE variable.
>>>
>>> Check the MAKEFLAGS variable to know automatically if the -j option is
>>> being used, but use the "=" operator instead of the ":=" operator
>>> because it can be checked only in a "recursively expanded variable".
I don't understand this part though. For QUIET we use :=, so why will it not
work for MAKE? Oh, of course, it's because -j does not appear in the global
MAKEFLAGS :-(
>>> Use "override" because otherwise it's impossible to change the
>>> automatic variable "MAKE".
>>>
>>> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
>>> ---
>>> Makefile | 4 ++--
>>> package/Makefile.in | 3 ++-
>>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/Makefile b/Makefile
>>> index 8d09725..6c2dcca 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -58,8 +58,8 @@ export HOSTARCH := $(shell uname -m | \
>>> #
>>> # Taking into account the above considerations, if you still want to execute
>>> # this top-level Makefile in parallel comment the ".NOTPARALLEL" line and
>>> -# build using the following command:
>>> -# make BR2_JLEVEL= -j$((`getconf _NPROCESSORS_ONLN`+1))
>>> +# use the -j<jobs> option when building, e.g:
>>> +# make -j$((`getconf _NPROCESSORS_ONLN`+1))
>>> .NOTPARALLEL:
>>>
>>> # absolute path
>>> diff --git a/package/Makefile.in b/package/Makefile.in
>>> index fc57427..ed68e35 100644
>>> --- a/package/Makefile.in
>>> +++ b/package/Makefile.in
>>> @@ -18,7 +18,8 @@ PARALLEL_JOBS := $(BR2_JLEVEL)
>>> endif
>>>
>>> MAKE1 := $(HOSTMAKE) -j1
>>> -MAKE := $(HOSTMAKE) $(if $(PARALLEL_JOBS),-j$(PARALLEL_JOBS))
>>> +override MAKE = $(HOSTMAKE) \
>>> + $(if $(findstring j,$(filter-out --%,$(MAKEFLAGS))),,-j$(PARALLEL_JOBS))
>>
>> Wouldn't it be much simpler to surround the definition of PARALLEL_JOBS at the
>> beginning of this file with
>>
>> ifeq ($(findstring j,$(filter-out --%,$(MAKEFLAGS))),)
>> ...
>> endif
>>
>> ?
>
> I don't know the reason but the MAKEFLAGS variable is empty if is
> checked inside the "ifeq" directive, so the only way I've found to
> check it is using the "$(if ,,)" function like what is done for the
> QUIET variable.
Right! It's actually not empty, but the -j flag is removed from it. I've done a
few tests and found no way to detect the -j flag at global scope.
> Also some packages, like boost and jack2 use the $(PARALLEL_JOBS)
> variable, if that variable isn't defined they fail to build.
Right, I forgot about that.
So, I tried the solution proposed in this patch extensively on a simple
Makefile to find out if everything is propagated correctly, and it seems to work
well. Therefore:
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2015-04-21 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 13:50 [Buildroot] [PATCH] packages: fix and improve support for top-level parallel makefile Fabio Porcedda
2015-04-20 3:27 ` Fabio Porcedda
2015-04-20 21:35 ` Arnout Vandecappelle
2015-04-21 3:01 ` Fabio Porcedda
2015-04-21 20:00 ` Arnout Vandecappelle [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=5536AC62.3020702@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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