From: Martin Dalecki <dalecki@evision-ventures.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Various kbuild problems in 2.5.22
Date: Wed, 19 Jun 2002 10:02:16 +0200 [thread overview]
Message-ID: <3D103A88.2050007@evision-ventures.com> (raw)
In-Reply-To: Pine.LNX.4.44.0206181056090.5695-100000@chaos.physics.uiowa.edu
Użytkownik Kai Germaschewski napisał:
> On Tue, 18 Jun 2002, Adam J. Richter wrote:
>
>
>> No, "make -k" still will not build bzImage if a module
>>fails to compile.
>>
>> Also, I do not understand why this is "intentional." Normally,
>>if one does a "make" of a file in a source tree, build problems with
>>unneeded files do not effect it.
>
>
> Yes, but they are not unneeded files, otherwise we wouldn't even try to
> build them. The point is, the semantics of bzImage changed: It now means
> "build bzImage and modules". That's the common case. If you really only
It is very inconenient if you are working only on some things
which don't affect any thing you are compiling as a module
during the edit/compile cycle or if you don't care to update
some modules you have just in case configured during developement.
How does one build the sole non modularized part of the kernel
nowadays? (Note: it is inconvenient now, but I'm not insisting.)
> want bzImage and no modules, you have to tell make by using
> "make KBUILD_MODULES= bzImage" (I could allow for phrasing the latter as
> "make bzImage nomodules", but that's only cosmetical)
next prev parent reply other threads:[~2002-06-19 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 15:00 Various kbuild problems in 2.5.22 Adam J. Richter
2002-06-18 16:14 ` Kai Germaschewski
2002-06-18 21:23 ` Gerd Knorr
2002-06-19 8:02 ` Martin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 3:07 Adam J. Richter
2002-06-19 2:55 Adam J. Richter
2002-06-19 2:50 Adam J. Richter
2002-06-19 2:56 ` Kai Germaschewski
2002-06-18 17:10 Adam J. Richter
2002-06-18 19:16 ` Sam Ravnborg
2002-06-18 19:28 ` Kai Germaschewski
2002-06-18 20:09 ` Sam Ravnborg
2002-06-18 12:18 Adam J. Richter
2002-06-18 14:24 ` Kai Germaschewski
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=3D103A88.2050007@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=adam@yggdrasil.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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