Re: [PATCH 0/2] kbuild updates

[Martin Schlemmer <azarah@nosferatu.za.org>]

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Sun, 2004-06-20 at 23:42, Arjan van de Ven wrote:
> > Given, but to 'use' the kbuild infrastructure, you must still call it
> > via:
> > 
> >   make -C _path_to_sources M=`pwd`
> 
> I see no problem with requiring this though; requiring a correct
> makefile is perfectly fine with me, and this is the only and documented
> way for 2.6 already.
> (And it's also the only way to build modules against Fedora Core 2
> kernels by the way)
> 

I did not mean I have a problem with that.  Say you take svgalib, and
you want the build system to automatically compile the kernel module,
you might do something like:

---
build_2_6_module:
	@make -C /lib/modules/`uname -r`/build M=`PWD`
---

will break with proposed patch ...

And the point I wanted to make was that AFIAK
'/lib/modules/`uname -r`/build' is an interface to figure
out where the _sources_ for the current running kernel are
located.  And apparently I am not the only one, as most if
not all external projects use this as the way (or one of
them at least) to determine this ... 


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]