From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: unset MAKEFLAGS
Date: Sun, 7 Jul 2013 21:38:25 +0200 [thread overview]
Message-ID: <20130707213825.170ad4fb@skate> (raw)
In-Reply-To: <1373222539-8915-1-git-send-email-s.martin49@gmail.com>
Dear Samuel Martin,
On Sun, 7 Jul 2013 20:42:19 +0200, Samuel Martin wrote:
> MAKEFLAGS can carry options that make Buildroot failed, eg. '-jN'.
> To avoid this, unset the MAKEFLAGS environment variable.
Does unsetting MAKEFLAGS really allows to prevent top-level parallel
build on Buildroot? Or does it only prevents MAKEFLAGS from leaking to
the sub-make calls that we do to build packages?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-07 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 18:42 [Buildroot] [PATCH] Makefile: unset MAKEFLAGS Samuel Martin
2013-07-07 19:38 ` Thomas Petazzoni [this message]
2013-07-07 20:09 ` Samuel Martin
2013-07-07 19:58 ` Peter Korsgaard
2013-07-07 20:14 ` Samuel Martin
2013-07-11 9:37 ` Thomas De Schampheleire
2013-07-11 10:33 ` Bjørn Forsman
2013-07-11 11:24 ` Thomas De Schampheleire
2013-07-11 11:46 ` Thomas Petazzoni
2013-07-11 12:02 ` Yann E. MORIN
2013-07-11 12:08 ` Thomas De Schampheleire
2013-07-11 12:17 ` Gustavo Zacarias
2013-07-12 17:07 ` Bjørn Forsman
2013-07-13 14:07 ` Thomas Petazzoni
2013-07-13 14:57 ` Bjørn Forsman
2013-07-11 11:01 ` Thomas Petazzoni
2013-07-11 11:36 ` Thomas De Schampheleire
2013-07-11 13:32 ` Thomas Petazzoni
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=20130707213825.170ad4fb@skate \
--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