Re: compiling only one module in kernel version 2.6?

["Randy.Dunlap" <rdunlap@xenotime.net>]

On Thu, 18 Aug 2005, Steven Rostedt wrote:

> On Thu, 2005-08-18 at 19:42 +0200, Sam Ravnborg wrote:
> > On Wed, Aug 17, 2005 at 01:54:50AM -0400, Steven Rostedt wrote:
> > > On Wed, 2005-08-17 at 01:48 -0400, Steven Rostedt wrote:
> > > > On Tue, 2005-08-16 at 22:41 -0700, Randy.Dunlap wrote:
> > > > >
> > > > > Sam only added make .ko build support very recently,
> > > > > so it could easily depend on what kernel verison Fong is using.
> > > >
> > > > That could very well explain it. I'm doing this on 2.6.13-rc6-rt6
> > > > (2.6.13-rc6 with Ingo's rt6 patch applied).  So I really do have a
> > > > recent kernel.
> > > >
> > >
> > > I just did this on a 2.6.9 vanilla kernel, and it still worked.
> >
> > Hi Steve.
> >
> > make fs/reiserfs/
> > and
> > make fs/reiserfs/resiserfs.ko
> >
> > does not do the same thing. Only the latter result in a .ko file.
>
> I never said I did a "make fs/reiserfs". I did a
> "make SUBDIRS=fs/reiserfs"  which does produce a .ko file.

That command uses an implicit target of all (which is
bzImage + modules), and then SUBDIRS (or M) limits it to
the specified subdir., so it builds all modules in the
specified subdir.
As opposed to what I thought(?) the OP was asking about:
how to build one module only.

I think that we have nailed it enough now, yes?  :)

> But even shorter is to do a "make M=fs/reiserfs", which also works.
>
> But, I guess what was added was the ability to just type the module
> itself.  That's cool, but I haven't had the need to do that (yet).

-- 
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/