aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLuis R. Rodriguez <mcgrof@winlab.rutgers.edu>2008-02-23 16:52:28 -0500
committerLuis R. Rodriguez <mcgrof@winlab.rutgers.edu>2008-02-23 16:52:28 -0500
commit16f91132a8927c9e4678eef94cf134f1a0b53f7c (patch)
tree83226ed4650438381ae3a701b62f6f24949b63f4
parentd0a3153c24dd7181b6cd22c47342279443472d0a (diff)
downloadcompat-wireless-2.6-old-16f91132a8927c9e4678eef94cf134f1a0b53f7c.tar.gz
It seems we need to be explicit about KMODPATH_ARG now, so lets
make sure we do that. Otherwise we'll get the build system to install our new modules in the kernel header's Makefile kernel release. This is what you would expect if you are building ontop of your own kernel sources but not ontop of your distribution's kernel. For example, on Ubuntu Hardy, which is on , you would get modules installed under the directory: /lib/modules/2.6.24-rc7/ This is because the Makefile /lib/modules/2.6.24-4-generic/build/Makefile had defined: VERSION = 2 PATCHLEVEL = 6 SUBLEVEL = 24 EXTRAVERSION = -rc7 What you really want is the modules to be installed instead under Signed-off-by: Luis R. Rodriguez <mcgrof@winlab.rutgers.edu>
-rw-r--r--Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile b/Makefile
index 3b6f0b5..18b8162 100644
--- a/Makefile
+++ b/Makefile
@@ -4,6 +4,7 @@ ifneq ($(origin $(KLIB)), undefined)
KMODPATH_ARG:= "INSTALL_MOD_PATH=$(KLIB)"
else
KLIB:= /lib/modules/$(shell uname -r)
+KMODPATH_ARG:= "INSTALL_MOD_PATH=$(KLIB)"
endif
KLIB_BUILD ?= $(KLIB)/build
MADWIFI=$(shell modprobe -l ath_pci)