From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 423] New: make -j X bzImage gives a warning
Date: Fri, 28 Feb 2003 13:38:51 -0800 [thread overview]
Message-ID: <362820000.1046468331@flay> (raw)
In-Reply-To: <20030228212504.GA21843@mars.ravnborg.org>
> On Fri, Feb 28, 2003 at 12:49:45PM -0800, Martin J. Bligh wrote:
>> http://bugme.osdl.org/show_bug.cgi?id=423
>>
>> Summary: make -j X bzImage gives a warning
>> Kernel Version: 2.5.63
>> Status: NEW
>> Severity: low
>> Owner: zippel@linux-m68k.org
>
> Feel free to bug me with kbuild related issues.
> In this area Roman is 'only' taking care of kconfig & related issues AFAIK.
>
>> make -j X bzImage gives a warning:
>>
>> make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make
>> rule.
>>
>> Can we get rid of this one way or the other?
>
> I have tried before - no luck.
> This one happens due to a $(Q)$(MAKE) used as part of a $(if
> construct in the top-level Makefile.
> See around line 335 - 345.
> It requires more than trivial changes to get rid of this one.
This bit?
define rule_vmlinux__
set -e
$(if $(filter .tmp_kallsyms%,$^),,
echo ' Generating build number'
. $(src)/scripts/mkversion > .tmp_version
mv -f .tmp_version .version
$(Q)$(MAKE) $(build)=init
)
$(call cmd,vmlinux__)
echo 'cmd_$@ := $(cmd_vmlinux__)' > $(@D)/.$(@F).cmd
endef
Is it possible to define $(SINGLE_MAKE) or something as well as $(MAKE),
where it strips the -j, and use that in the instances where it can't
take a -j? Would be nice to get rid of that one last warning ... ;-)
M.
next prev parent reply other threads:[~2003-02-28 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 20:49 [Bug 423] New: make -j X bzImage gives a warning Martin J. Bligh
2003-02-28 21:25 ` Sam Ravnborg
2003-02-28 21:38 ` Martin J. Bligh [this message]
2003-03-02 18:38 ` Sam Ravnborg
2003-03-02 18:54 ` Martin J. Bligh
2003-02-28 22:29 ` Roman Zippel
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=362820000.1046468331@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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