Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...
On Sun, Apr 12, 2009 at 08:10:13PM +0200, Sven Joachim wrote: I see. The VERSION variable is supposed to be set by including /usr/share/modass/include/generic.make, and you apparently do not have module-assistant installed, do you? Probably nvidia-kernel-source should stop recommending kernel-package and just depend on module-assistant like every other $module-source package does. That seems like a great idea. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...
On Sun, Apr 12, 2009 at 01:48:27PM -0400, Christopher Martin wrote: On April 12, 2009 13:36:36 Sven Joachim wrote: Only because $(VERSION) is empty for you, and that is the problem. How did you try to build the module? I tried: cd /usr/src/modules/nvidia-kernel (after unpacking /usr/src/nvidia-kernel.tar.bz2) KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. This is what I've done for a long time (changing the kernel in question each time, obviously). Why not use module-assitant? I sure didn't test that old way of doing it when I rewrote the build scripts. I used module-assistant and a hacked up version of linux-modules-nonfree-2.6 and both worked. I did not test make-kpkg or doing it manually (which I stopped doing years ago when I discovered module-assistant). -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Bug#523716: Another build failure...
KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. The strange thing here is that is how I tested mine (and didn't see the dh_clean problem). -- Randall Donald ra...@khensu.org http://www.khensu.orgrdon...@debian.org Programmer/Debian Developer GnuPG: 6C27DEAB -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...
On April 13, 2009 11:14:12 Lennart Sorensen wrote: That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. This is what I've done for a long time (changing the kernel in question each time, obviously). Why not use module-assitant? I sure didn't test that old way of doing it when I rewrote the build scripts. I used module-assistant and a hacked up version of linux-modules-nonfree-2.6 and both worked. I did not test make-kpkg or doing it manually (which I stopped doing years ago when I discovered module-assistant). I guess I'll switch to module-assistant - not a problem. But as was pointed out elsewhere, it might be best to make the requirement explicit. Cheers, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: [pkg-nvidia-devel] Bug#523716: Bug#523716: Another build failure...
On Mon, Apr 13, 2009 at 08:44:27AM -0700, Randall Donald wrote: KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. The strange thing here is that is how I tested mine (and didn't see the dh_clean problem). Did you remember to rm -rf /usr/src/modules/nvidia-* between runs to avoid any existing files there from contaminating the test? -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...
On Mon, Apr 13, 2009 at 12:39:17PM -0400, Christopher Martin wrote: I guess I'll switch to module-assistant - not a problem. But as was pointed out elsewhere, it might be best to make the requirement explicit. Yeah it should be. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Bug#523716: Another build failure...
On Mon, 2009-04-13 at 14:07 -0400, Lennart Sorensen wrote: On Mon, Apr 13, 2009 at 08:44:27AM -0700, Randall Donald wrote: KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules That is no longer a complete set of headers and you can't build against it like that. The kernel team says that is no longer supported. The strange thing here is that is how I tested mine (and didn't see the dh_clean problem). Did you remember to rm -rf /usr/src/modules/nvidia-* between runs to avoid any existing files there from contaminating the test? Yup. I will try again though. Maybe I am on crack. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: [pkg-nvidia-devel] Bug#523716: Bug#523716: Another build failure...
On Mon, Apr 13, 2009 at 01:28:26PM -0700, Randall Donald wrote: On Mon, 2009-04-13 at 14:07 -0400, Lennart Sorensen wrote: Yup. I will try again though. Maybe I am on crack. Or perhaps I am wrong and it still works. I will have a look at whether make-kpkg still works or not, since it should be simple to fix if it doesn't. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: Another build failure...
My build (180.44-1) also failed here: dh_installdocs dh_installmodules dh_installchangelogs dh_installmodules dh_strip dh_compress dh_fixperms dh_installdeb dh_gencontrol -- -v dpkg-gencontrol: unknown option `-v' Usage: dpkg-gencontrol [option ...] Options: -ppackage print control file for package. -ccontrolfile get control info from this file. -lchangelogfileget per-version info from this file. -Fchangelogformat force change log format. -vforceversion set version of binary package. -ffileslistfilewrite files here instead of debian/files. -Ppackagebuilddir temporary build dir instead of debian/tmp. -nfilename assume the package filename will be filename. -O write to stdout, not .../DEBIAN/control. -is, -ip, -isp, -ips deprecated, ignored for compatibility. -Dfield=valueoverride or add a field and value. -Ufieldremove a field. -Vname=value set a substitution variable. -Tvarlistfile read variables here, not debian/substvars. -h, --help show this help message. --versionshow the version. dh_gencontrol: dpkg-gencontrol returned exit code 2 make: *** [binary-modules] Error 1 --- I simply edited debian/rules to change dh_gencontrol -- -v$(VERSION) into dh_gencontrol -- $(VERSION). Seems to work... Hopefully these little glitches can be fixed up soon. Thanks, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: Another build failure...
On 2009-04-12 15:15 +0200, Christopher Martin wrote: My build (180.44-1) also failed here: dh_installdocs dh_installmodules dh_installchangelogs dh_installmodules dh_strip dh_compress dh_fixperms dh_installdeb dh_gencontrol -- -v Strange, I get dh_gencontrol -- -v180.44-1+custom.1.2 at this stage (the custom.1.2 being the Debian revision of my linux-image package). dpkg-gencontrol: unknown option `-v' This error message is misleading, since -v is actually a known option, but the version argument is missing. Usage: dpkg-gencontrol [option ...] Options: -ppackage print control file for package. -ccontrolfile get control info from this file. -lchangelogfileget per-version info from this file. -Fchangelogformat force change log format. -vforceversion set version of binary package. -ffileslistfilewrite files here instead of debian/files. -Ppackagebuilddir temporary build dir instead of debian/tmp. -nfilename assume the package filename will be filename. -O write to stdout, not .../DEBIAN/control. -is, -ip, -isp, -ips deprecated, ignored for compatibility. -Dfield=valueoverride or add a field and value. -Ufieldremove a field. -Vname=value set a substitution variable. -Tvarlistfile read variables here, not debian/substvars. -h, --help show this help message. --versionshow the version. dh_gencontrol: dpkg-gencontrol returned exit code 2 make: *** [binary-modules] Error 1 --- I simply edited debian/rules to change dh_gencontrol -- -v$(VERSION) into dh_gencontrol -- $(VERSION). Seems to work... Only because $(VERSION) is empty for you, and that is the problem. How did you try to build the module? Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: Another build failure...
On April 12, 2009 13:36:36 Sven Joachim wrote: Only because $(VERSION) is empty for you, and that is the problem. How did you try to build the module? I tried: cd /usr/src/modules/nvidia-kernel (after unpacking /usr/src/nvidia-kernel.tar.bz2) KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules This is what I've done for a long time (changing the kernel in question each time, obviously). Hope that helps, Christopher Martin signature.asc Description: This is a digitally signed message part.
Bug#523716: Another build failure...
On 2009-04-12 19:48 +0200, Christopher Martin wrote: On April 12, 2009 13:36:36 Sven Joachim wrote: Only because $(VERSION) is empty for you, and that is the problem. How did you try to build the module? I tried: cd /usr/src/modules/nvidia-kernel (after unpacking /usr/src/nvidia-kernel.tar.bz2) KSRC=/usr/src/linux-headers-2.6.29-1-686-bigmem \ KVERS=2.6.29-1-686-bigmem debian/rules binary_modules This is what I've done for a long time (changing the kernel in question each time, obviously). I see. The VERSION variable is supposed to be set by including /usr/share/modass/include/generic.make, and you apparently do not have module-assistant installed, do you? Probably nvidia-kernel-source should stop recommending kernel-package and just depend on module-assistant like every other $module-source package does. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523716: Another build failure...
On April 12, 2009 14:10:13 Sven Joachim wrote: I see. The VERSION variable is supposed to be set by including /usr/share/modass/include/generic.make, and you apparently do not have module-assistant installed, do you? Probably nvidia-kernel-source should stop recommending kernel-package and just depend on module-assistant like every other $module-source package does. Correct, I don't have module-assistant installed. signature.asc Description: This is a digitally signed message part.
