Re: building a specific in-tree module is currently a bit broken

["Robert P. J. Day" <rpjday@mindspring.com>]

On Wed, 5 Sep 2007, Jan Engelhardt wrote:

>
> On Sep 5 2007 05:42, Robert P. J. Day wrote:
> >that doesn't solve the problem.  i should have mentioned that i
> >already (unnecessarily, i suggest) ran "make modules_prepare", but
> >the problem persists.
> >
> >the issue seems to be that running that last make command to build
> >the module visor.ko doesn't somehow signal the Makefile that this
> >is a *module* build, and therefore no module-related initialization
> >is done, such as creating that directory or setting the Makefile
> >variable MODVERDIR, etc, etc.
>
> ah... make M=drivers/foo/bar/
> it builds the whole directory, but at least it builds it.

oh, i know *that* works but, as you can see, that make command has
enough info (the "M=" variable) to kick the Makefile into
module-building mode, so things work properly.

the original problem, of course, is still there.  but i think i've
flogged this sufficiently.  i'll leave someone else to do the fixing.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
-
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/