From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] packages: fix and improve support for top-level parallel makefile
Date: Fri, 26 Jun 2015 20:09:49 +0200 [thread overview]
Message-ID: <20150626200949.64342552@free-electrons.com> (raw)
In-Reply-To: <1435291134-6780-2-git-send-email-fabio.porcedda@gmail.com>
Dear Fabio Porcedda,
On Fri, 26 Jun 2015 05:58:53 +0200, Fabio Porcedda wrote:
> To fix packages that fail to build when PARALLEL_JOBS is empty instead
Which packages specifically?
> of using an empty PARALLEL_JOBS just avoid to using it in
s/avoid to/avoid/
> MAKE1 := $(HOSTMAKE) -j1
> -MAKE := $(HOSTMAKE) $(if $(PARALLEL_JOBS),-j$(PARALLEL_JOBS))
> +override MAKE = $(HOSTMAKE) \
> + $(if $(findstring j,$(filter-out --%,$(MAKEFLAGS))),,-j$(PARALLEL_JOBS))
Why should we force to not use make -j for each individual package when
top-level parallel build is used ? Maybe for some scenarios it is better
to have 2 top-level jobs, and then 2 jobs per package ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-26 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 3:58 [Buildroot] [PATCH v4 0/2] Top-level parallel makefile improvements Fabio Porcedda
2015-06-26 3:58 ` [Buildroot] [PATCH v4 1/2] packages: fix and improve support for top-level parallel makefile Fabio Porcedda
2015-06-26 18:09 ` Thomas Petazzoni [this message]
2015-06-26 19:39 ` Fabio Porcedda
2015-06-27 14:10 ` Thomas Petazzoni
2015-06-28 16:26 ` Fabio Porcedda
2015-06-26 3:58 ` [Buildroot] [PATCH v4 2/2] pkg-luarocks: fix top-level parallel makefile support Fabio Porcedda
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=20150626200949.64342552@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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