From: Fabio Porcedda <fabio.porcedda@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] package/Makefile.in: add a way to don't force jobs in sub-make
Date: Tue, 10 Sep 2013 09:46:02 +0200 [thread overview]
Message-ID: <1378799164-28645-2-git-send-email-fabio.porcedda@gmail.com> (raw)
In-Reply-To: <1378799164-28645-1-git-send-email-fabio.porcedda@gmail.com>
When the "BR2_JLEVEL" variable is empty use "make"
without the "-j" option.
To be able to use top-level parallel make we must don't force
the number of jobs in sub-make.
Example:
make BR2_JLEVEL= -j8
Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
package/Makefile.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/Makefile.in b/package/Makefile.in
index 91ae1b9..6702df4 100644
--- a/package/Makefile.in
+++ b/package/Makefile.in
@@ -18,7 +18,7 @@ PARALLEL_JOBS:=$(BR2_JLEVEL)
endif
MAKE1:=$(HOSTMAKE) -j1
-MAKE:=$(HOSTMAKE) -j$(PARALLEL_JOBS)
+MAKE:=$(HOSTMAKE) $(if $(PARALLEL_JOBS),-j$(PARALLEL_JOBS))
# Compute GNU_TARGET_NAME
GNU_TARGET_NAME=$(ARCH)-buildroot-$(TARGET_OS)-$(LIBC)$(ABI)
--
1.8.4
next prev parent reply other threads:[~2013-09-10 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 7:46 [Buildroot] [PATCH v3 0/3] Fix for top-level parallel make part 1 Fabio Porcedda
2013-09-10 7:46 ` Fabio Porcedda [this message]
2013-09-12 18:28 ` [Buildroot] [PATCH v3 1/3] package/Makefile.in: add a way to don't force jobs in sub-make Thomas Petazzoni
2013-09-10 7:46 ` [Buildroot] [PATCH v3 2/3] pkg-generic: fix rules for top-level parallel make Fabio Porcedda
2013-09-10 7:46 ` [Buildroot] [PATCH v3 3/3] package: add toolchain dependency to inner-generic-package 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=1378799164-28645-2-git-send-email-fabio.porcedda@gmail.com \
--to=fabio.porcedda@gmail.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