Hi, On Tue, Oct 22, 2002 at 01:07:24PM +0200, Michel Dänzer wrote: > The gotcha about TREE is that you have to provide the include directory, so > you'd have to use TREE=/home/mcornils/kernel-source-2.4.18/include in this case.
Errm, is this documented somewhere? Couldn't this be part of the install script? Maybe with an option to specify a correct TREE before the kernel module compilation starts? > Already is, from Makefile.linux: > > A := /lib/modules/$(VERSION)/build/include > B := /usr/src/linux-$(VERSION)/include > C := /usr/src/linux/include > D := /usr/include Ah, cool. > If TREE isn't specified by the user, these are tried in this order. IMHO > only the first one is sensible, but I definitely vote for removing the > last one as only broken systems will have kernel headers in > /usr/include, on sane systems compilation will be attempted and fail. hmm, weird. Compilation should have worked then after I changed /usr/src/linux to my current kernel tree; I wonder why this didn't succeed. I'll retry eventually and I'll report if it doesn't work. -Malte #8-) ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
