From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] query about change to $(MAKE) definition
Date: Tue, 8 Jul 2008 10:26:13 +0200 [thread overview]
Message-ID: <20080708082613.GC21132@mx.loc> (raw)
In-Reply-To: <87abgsu6x1.fsf@macbook.be.48ers.dk>
On Tue, Jul 08, 2008 at 10:16:58AM +0200, Peter Korsgaard wrote:
>>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
>The easiest would actually be if would get rid of the BR2_JLEVEL stuff
>completely and just let people use -j<whatever> on the top level make
>instead, then make should handle it all automatically. Why don't we do
>it like that? Is something in the toplevel makefile broken for
>parallel builds? (I know lots of other buildroot stuff is broken for
>parallel). Then we could also get rid of the HOSTMAKE thing and it
>would all boil down to:
>
>MAKE1=$(MAKE) -j1
>
>What do you say?
See ML archives where i talked about parallel builds and toplevel
parallel builds.
HTH,
next prev parent reply other threads:[~2008-07-08 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 7:10 [Buildroot] query about change to $(MAKE) definition Hamish Moffatt
2008-07-08 8:16 ` Peter Korsgaard
2008-07-08 8:26 ` Bernhard Fischer [this message]
2008-07-08 9:02 ` Peter Korsgaard
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=20080708082613.GC21132@mx.loc \
--to=rep.dot.nop@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