Thanks for explanation, i just updated the package!
Search Criteria
Package Details: dkms-pl2501 20121021-2
Package Actions
| Package Base: | dkms-pl2501 |
|---|---|
| Description: | DKMS-controlled kernel driver for PL-2501 USB Easy Trasfer Cables |
| Upstream URL: | https://patchwork.kernel.org/patch/1227361/ |
| Category: | modules |
| Licenses: | |
| Submitter: | kyak |
| Maintainer: | kyak |
| Last Packager: | None |
| Votes: | 2 |
| First Submitted: | 2012-10-21 18:38 |
| Last Updated: | 2013-03-23 07:32 |
Latest Comments
Comment by kyak
Anonymous comment
Actually, it does work, but in this case it's not the desired behaviour. KERNELRELEASE is defined when the -k option is passed to dkms (it seems so, I might be wrong). What I meant is that trying to build the module for a kernel other than the current (e.g. a new release immediately after an update) will still result in an attempt to build it for the current one.
Comment by kyak
Strange, i don't have this problem here (3.8.2-1-ck).
Can you explain more why $(shell uname -r) doesn't work if KERNELRELEASE is defined?
Anonymous comment
The makefile doesn't work with autoinstall after a kernel update. Changing
KRELEASE := $(shell uname -r)
to
ifndef KERNELRELEASE
KRELEASE := $(shell uname -r)
else
KRELEASE := $(KERNELRELEASE)
endif
seems to solve the problem.