Bug#523716: [pkg-nvidia-devel] Bug#523716: Another build failure...

2009-04-13 Thread Lennart Sorensen
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...

2009-04-13 Thread Lennart Sorensen
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: Another build failure...

2009-04-13 Thread Christopher Martin
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: Another build failure...

2009-04-13 Thread Lennart Sorensen
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