mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Subject: Replacement for "make SUBDIRS=...." in 2.5.63?
Date: Mon, 24 Feb 2003 22:33:39 -0800	[thread overview]
Message-ID: <200302250633.WAA06979@adam.yggdrasil.com> (raw)

	I see that if I do something like "make SUBDIRS=net/ipv4 modules",
I get warnings like:

*** Warning: Overriding SUBDIRS on the command line can cause inconsistencies
*** Uh-oh, you have stale module entries. You messed with SUBDIRS

	What is the proper way to rebuild just one subdirectory?  How
about for building externally provided modules?  Is this is a new
limitation of kbuild?  If so, I think it will reduce my productivity,
and probably developer productivity on average.  I need to rebuild
small sets of modules or core kernel subdirectories frequently.  I'd
like to know what benefits I get from this so that I can measure
whether this really saves me time somehow.

	I suspect that this was added to support putting module
dependencies into the ".ko" files, which might be underlying issue
that needs a cost/benefit review, but perhaps there is some other
factor that I'm just unaware of.

	Any answers to these questions would be appreciated.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2003-02-25  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  6:33 Adam J. Richter [this message]
2003-02-25 17:04 ` Kai Germaschewski
2003-02-28 12:48   ` Gerd Knorr
2003-02-28 16:05   ` David Woodhouse
2003-02-25 19:26 Adam J. Richter

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=200302250633.WAA06979@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --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

all inboxes | Powered by JetHome®