Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Porcedda <fabio.porcedda@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9 8/8] Makefile: update comment about top-level parallel Makefile
Date: Fri, 15 Nov 2013 15:40:22 +0100	[thread overview]
Message-ID: <1384526422-30142-9-git-send-email-fabio.porcedda@gmail.com> (raw)
In-Reply-To: <1384526422-30142-1-git-send-email-fabio.porcedda@gmail.com>

After the latest patches top-level parallel Makefile is working but
there are still issues when the building order is changed so change
the comment to explain that.

Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
---
 Makefile | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/Makefile b/Makefile
index ae8b087..17a6ef2 100644
--- a/Makefile
+++ b/Makefile
@@ -42,7 +42,18 @@ export HOSTARCH := $(shell uname -m | \
 	    -e s/macppc/powerpc/\
 	    -e s/sh.*/sh/)
 
-# This top-level Makefile can *not* be executed in parallel
+# The parallel execution of this top-level Makefile is disabled
+# because it would change the package building order, that can be a
+# problem because some packages can have unspecified optional
+# dependencies so if those dependencies are present when the package
+# is built, they are used, otherwise they aren't (but compilation
+# happily proceeds). This means that the package order is relevant in
+# that case, and the end result will differ if the order is swapped
+# due to parallel building.
+# Taking in account the above warnings, if you still want to execute
+# this top-level Makefile in parrallel comment the following
+# line and execute:
+#	make BR2_JLEVEL= -j$((`getconf _NPROCESSORS_ONLN`+1))
 .NOTPARALLEL:
 
 # absolute path
-- 
1.8.4.2

      parent reply	other threads:[~2013-11-15 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 14:40 [Buildroot] [PATCH v9 0/8] Add support for top-level parallel make Fabio Porcedda
2013-11-15 14:40 ` [Buildroot] [PATCH v9 1/8] package: add base dependency to every package Fabio Porcedda
2013-11-17 13:18   ` Arnout Vandecappelle
2013-11-15 14:40 ` [Buildroot] [PATCH v9 2/8] package: add toolchain dependency to every target package Fabio Porcedda
2013-11-17 13:52   ` Arnout Vandecappelle
2013-11-15 14:40 ` [Buildroot] [PATCH v9 3/8] package: add support for top-level parallel make Fabio Porcedda
2013-11-15 14:40 ` [Buildroot] [PATCH v9 4/8] uclibc: " Fabio Porcedda
2013-11-15 14:40 ` [Buildroot] [PATCH v9 5/8] glibc: " Fabio Porcedda
2013-11-15 14:40 ` [Buildroot] [PATCH v9 6/8] Makefile: " Fabio Porcedda
2013-11-15 14:40 ` [Buildroot] [PATCH v9 7/8] package: enable jobserver for recursive make Fabio Porcedda
2013-11-15 14:40 ` Fabio Porcedda [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=1384526422-30142-9-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