Bug#345918: linux-2.6: modules do not install to correct folder in /lib/modu

["Richard Burton" <richardaburton@hotmail.com>]

> Congratulations, you are the first to file a bug report against linux 
> 2.6.15 :)

Yay ;-)

> Could you tell us exactly what you do to build the module, and check if 
> this
> is not a bug in m-a or your module ?
> The official recomended way of building modules is to build inside the 
> module
> tree with KSRC=/lib/modules/2.6.15-1-686/build, is this the way you do it ?

Here are a couple of extracts from the tp_smapi makefile which should show 
how it's done (I use 'make install' to drive this):

KVER := $(shell uname -r)
KDIR := /lib/modules/$(KVER)/build
PWD := $(shell pwd)
MDIR   := drivers/firmware
...
modules: $(patsubst %.o,%.c,$(TP_MODULES))
       $(MAKE) -C $(KDIR) M=$(PWD) modules
...
install: modules
       rm -f /lib/modules/$(KVER)/kernel/$(MDIR)/{tp_base,tp_smapi}.ko
       $(MAKE) -C $(KDIR) M=$(PWD) modules_install
       depmod -a

> Did it work for the official 2.6.14-[12] debian kernels ? Did it work for
> another kernel ?

No, it was the same at 2.6.14, don't know about earlier than that.

Also worth noting is that it looks from the makefile (the rm before the 
make, using MDIR) as though the modules should get installed in 
/lib/modules/2.6.15-1-686/kernel/drivers/firmware, but they actually end up 
in /lib/modules/2.6.15-1/extras, not sure if that's another build system 
problem, or if it is an issue with the makefile though???

Richard.