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
Date: Thu, 1 Nov 2007 19:05:53 +0100 [thread overview]
Message-ID: <20071101180553.GB3312@uranus.ravnborg.org> (raw)
In-Reply-To: <1193938746.7555.7.camel@localhost>
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
next prev parent reply other threads:[~2007-11-01 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 17:39 Chris Holvenstot
2007-11-01 17:51 ` Adrian Bunk
2007-11-01 18:03 ` Chris Holvenstot
2007-11-01 18:05 ` Sam Ravnborg [this message]
2007-11-01 18:12 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071101180553.GB3312@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=cholvenstot@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®