From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [Bug 423] New: make -j X bzImage gives a warning
Date: Sun, 02 Mar 2003 10:54:13 -0800 [thread overview]
Message-ID: <48930000.1046631252@[10.10.2.4]> (raw)
In-Reply-To: <20030302183857.GA8094@mars.ravnborg.org>
--On Sunday, March 02, 2003 19:38:57 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
> On Fri, Feb 28, 2003 at 01:38:51PM -0800, Martin J. Bligh wrote:
>> > 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
>> >> 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?
>
> Kai has fixed this one in bk-latest.
>
> Sample run:
>
> [sam@mars kbuild4]$ make -j2 bzImage
> make[1]: `scripts/kconfig/conf' is up to date.
> ./scripts/kconfig/conf -s arch/i386/Kconfig
>#
># using defaults found in .config
>#
> SPLIT include/linux/autoconf.h -> include/config/*
> Starting the build. KBUILD_BUILTIN=1 KBUILD_MODULES=
> GEN include/linux/compile.h (unchanged)
> Kernel: arch/i386/boot/bzImage is ready
Heh - very cool. Tested it out. Thanks Kai ...
I'll close that bug.
M.
next prev parent reply other threads:[~2003-03-02 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 20:49 Martin J. Bligh
2003-02-28 21:25 ` Sam Ravnborg
2003-02-28 21:38 ` Martin J. Bligh
2003-03-02 18:38 ` Sam Ravnborg
2003-03-02 18:54 ` Martin J. Bligh [this message]
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='48930000.1046631252@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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
all inboxes | Powered by JetHome®