Hi,
Here it is :
$ head -n5 ./debian/changelog
linux-source-2.6.14 (lala16) unstable; urgency=low
* It was pointed out to me that the ability to build third party modules
using make-kpkg and linux kernel headers packages had broken with
recent kernel packages, since the check for whether we were in a top
"lala16" is make-kpkg's --revision value, it appears only in the package
filename.
I made another attemp :
# make-kpkg clean
# make-kpkg --append-to-version='-mat2' --revision=lala17 kernel_image
...
# head -n1 ./debian/changelog
linux-source-2.6.14-mat2 (lala17) unstable; urgency=low
# grep LOCALVERSION= .config
CONFIG_LOCALVERSION="-matt"
build my nvidia module :
# make-kpkg modules_image
exec debian/rules DEBIAN_REVISION=lala17 modules_image
====== making .config because of Makefile ======
test -f .config || test ! -f .config.save || \
cp -pf .config.save .config
test -f .config || test ! -f .config || \
cp -pf .config .config
test -f .config || test ! -f ./debian/config || \
cp -pf ./debian/config .config
test -f .config || (echo "*** Need a config file .config" && false)
The changelog says we are creating 2.6.14-mat2, but I thought the
version is 2.6.14
make: *** [modules_image] Erreur 1
# make-kpkg --append-to-version='-mat2' modules_image
Warning: The file include/linux/version.h exists
The contained UTS_VERSION string:
"2.6.14-mat2-matt"
does not match expectations:
"2.6.14-mat2"
...
Finaly I have :
linux-image-2.6.14-mat2_lala17_i386.deb
nvidia-kernel-2.6.14-mat2_1.0.8178-2+lala17_i386.deb
Path for modules are (same order as above) :
/lib/modules/2.6.14-mat2-matt/kernel/...
/lib/modules/2.6.14-mat2/nvidia/...
Regards,
Matthieu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
