Date: Thu, 1 Nov 2007 19:05:53 +0100
From: Sam Ravnborg <sam@ravnborg.org>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Issue building kernel driver
Message-ID: <20071101180553.GB3312@uranus.ravnborg.org>
References: <1193938746.7555.7.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1193938746.7555.7.camel@localhost>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1294
Lines: 30

On Thu, Nov 01, 2007 at 12:39:06PM -0500, Chris Holvenstot wrote:
> 
> Although it may not be popular with the crowd here, I do have a valid
> reason to run Windows - and I accomidate this using the VirtualBox
> product.  
> 
> Since I try to be slightly useful and build as many of the "test" kernel
> images I can I end up rebuilding the VirtualBox kernel driver (open
> source) on an almost daily basis.

We had an report about the vbox package a few days ago.
I looked at it and the vbox code is so ugly that it was not fun at all.
They play some very strange games in their include hell and that is
obviously doomed to do so.
You are unfortunately as a user hit by this and the only
recommendation I have is to report it back to the vbox people.
Fixing vbox may be trivial if you dive into their include hell
but I do think you are better off talking to the vbox people here.

They may say that "the kernel changed - fix the kernel" but we have the
~1800 modules building in the kernel so they need to fix their end of stuff. 

Good luck,

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/