Re: Mainline kernel source curiosity

[Stephen Powell <zlinuxman@wowway.com>]

On Mon, 20 Sep 2010 13:50:12 -0400 (EDT), Kumar Appaiah wrote:
> On Mon, Sep 20, 2010 at 01:25:45PM -0400, Curt Howland wrote:
>> ==========
>> Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not
>> match the current kernel (version 2.6.36-rc4-curt1.0).  Stop.
>> ==========
>> 
>> The thing is, there is no such error with 2.6.35.4-curt1.0, nor when
>> it was 35-rc4-curt1.0.
>> 
>> So why would it be choking on the custom extension now? I used
>> _exactly_ the same compile command, listed above.
> 
> 
> Is this a manifestation of this:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591793
> 
> I am unsure, but I was under the impression that kernel-package is
> broken for the most recent kernels.

Curt, I don't know if this is related to the problem or not, but make
sure that you don't have CONFIG_LOCALVERSION or CONFIG_LOCALVERSION_AUTO
set in your kernel configuration file and make sure that you specify
--append-to-version and --revision on *every* invocation of make-kpkg.  How
are you creating the virtualbox and nvidia packages?  Are you using
module-assistant?  Or are you compiling a kernel source module package
using the modules_image target of make-kpkg?  If you are using
module-assistant (which I don't recommend if you are building
out-of-kernel-source-tree kernel module packages for a custom kernel)
then you will need to use the kernel_headers target as well as
the kernel_image target, then install both before moving on to
create the modules package.

It is best to install the Debian
out-of-kernel-source-tree kernel module source package and use the
kernel_image and modules_image targets.  Then you don't have to
create or install kernel header packages.

HTH

-- 
  .''`.     Stephen Powell    
 : :'  :
 `. `'`
   `-