public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Various kbuild problems in 2.5.22
Date: 18 Jun 2002 21:23:55 GMT	[thread overview]
Message-ID: <slrnagv97b.1r4.kraxel@bytesex.org> (raw)
In-Reply-To: Pine.LNX.4.44.0206181056090.5695-100000@chaos.physics.uiowa.edu

>  Apart from that, "make modules_install" never worked in the case of 
>  failed builds, did it? - so it boils down to: you need a buildable .config 
>  to build and test a kernel.

No.  2.4.x allows me to to "make modules_install" even if some modules
don't work.  My kernel build script compiles the modules with "make -k
modules", and if some non-essential modules doesn't build I can simply
ignore that and go ahead.  There is no need to disable that module
temporarely in .config (and risc to forget to reenable it later ...).

  Gerd

-- 
You can't please everybody.  And usually if you _try_ to please
everybody, the end result is one big mess.
				-- Linus Torvalds, 2002-04-20

  reply	other threads:[~2002-06-18 21:55 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 [this message]
2002-06-19  8:02   ` Martin Dalecki
  -- 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=slrnagv97b.1r4.kraxel@bytesex.org \
    --to=kraxel@bytesex.org \
    --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