On Wed, Jan 04, 2006 at 10:50:19AM +0000, Richard Burton wrote: > > >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
We use $(MAKE) KSRC=/lib/modules/$(KVER)/build to build and install, i believe. have you seen other modules and can you confirm they don't break or something such ? I know there are a couple of them that work, and i thus believe upto a point that it is a bug in this module, as well as a lack of correct documentation on our part probably. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]