[pkg-nvidia-devel] nvidia-graphics-drivers-legacy-173xx still dislikes me

[Randall Donald]

On Fri, 2009-06-05 at 11:46 -0400, John A Martin wrote:

> Following the README-Debian instructions dies almost immediately with
> 
> athene:/usr/src/modules/nvidia-kernel-legacy-173xx# debian/rules binary_modules
> make: *** No rule to make target `binary_modules'.  Stop.
> 

That is a known issue. Those directions don't work currently.


> and more interestingly:
> 
> ,----[ m-a -t a-i nvidia-kernel-legacy-173xx ]
> .
> Updated infos about 1 packages
> Getting source for kernel version: 2.6.29-2-686
> Kernel headers available in /lib/modules/2.6.29-2-686/build
> apt-get install build-essential 
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> build-essential is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 
> Done!
> unpack 
> Extracting the package tarball, /usr/src/nvidia-kernel-legacy-173xx.tar.bz2, please wait...
> "/usr/share/modass/packages/default.sh" build KVERS=2.6.29-2-686 KSRC=/lib/modules/2.6.29-2-686/build KDREV=2.6.29-5 kdist_image
> /usr/bin/make -C . LINUXDIR=/lib/modules/2.6.29-2-686/build KVERREL=2.6.29-2-686 clean
> make[1]: Entering directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> rm -rf *.o *.ko .depend .*.flags .*.d .*.cmd *.mod.c .tmp_versions
> make[1]: Leaving directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> dh_clean
> /usr/bin/make  -f debian/rules kdist_clean kdist_config binary-modules
> make[1]: Entering directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> /usr/bin/make -C . LINUXDIR=/lib/modules/2.6.29-2-686/build KVERREL=2.6.29-2-686 clean
> make[2]: Entering directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> rm -rf *.o *.ko .depend .*.flags .*.d .*.cmd *.mod.c .tmp_versions
> make[2]: Leaving directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> dh_clean
> /usr/bin/make -w -f debian/rules configure
> make[2]: Entering directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> sed 's/#KVERS#/2.6.29-2-686/g' debian/control.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/control
> sed 's/#KVERS#/2.6.29-2-686/g' debian/dirs.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/dirs
> sed 's/#KVERS#/2.6.29-2-686/g' debian/override.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/override
> make[2]: Leaving directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> sed 's/#KVERS#/2.6.29-2-686/g' debian/control.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/control
> sed 's/#KVERS#/2.6.29-2-686/g' debian/dirs.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/dirs
> sed 's/#KVERS#/2.6.29-2-686/g' debian/override.template > /usr/src/modules/nvidia-kernel-legacy-173xx/debian/override
> dh_testroot
> dh_prep
> # Build the modules
> /usr/bin/make -C . LINUXDIR=/lib/modules/2.6.29-2-686/build KVERREL=2.6.29-2-686
> make[2]: Entering directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> make -C /lib/modules/2.6.29-2-686/build  M=`/bin/pwd` modules
> make[3]: Entering directory `/usr/src/linux-headers-2.6.29-2-686'
> /usr/src/linux-headers-2.6.29-2-common/Makefile:284: /usr/src/linux-headers-2.6.29-2-common/scripts/Kbuild.include: No such file or directory
> /bin/sh: line 0: [: -lt: unary operator expected
> make: *** empty variable name.  Stop.
> make[5]: *** [_module_/usr/src/modules/nvidia-kernel-legacy-173xx] Error 2
> make[4]: *** [sub-make] Error 2
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/usr/src/linux-headers-2.6.29-2-686'
> make[2]: *** [modules] Error 2
> make[2]: Leaving directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> make[1]: *** [binary-modules] Error 2
> make[1]: Leaving directory `/usr/src/modules/nvidia-kernel-legacy-173xx'
> make: *** [kdist_build] Error 2
> BUILD FAILED!
> See /var/cache/modass/nvidia-kernel-legacy-173xx-source.buildlog.2.6.29-2-686.1244206400 for details.
> Build failed. Press Return to continue...
> 
> `----
> 
> Can you suggest something else to try or a workaround?
> 

Unfortunately I don't have my unstable system working right now so I
can't test this. Maybe one of the other team members could help.


-- 
--------------------------------------------
Randall Donald             randy at khensu.org
http://www.khensu.org    rdonald at debian.org
Programmer/Debian Developer GnuPG: 6C27DEAB
--------------------------------------------