From: walt <w41ter@gmail.com>
To: kvm@vger.kernel.org
Subject: Preventing conflicts between kernel header versions?
Date: Sat, 08 Nov 2008 16:36:25 -0800 [thread overview]
Message-ID: <gf5bac$frp$1@ger.gmane.org> (raw)
Hi kvm team,
I'm tracking Linus.git, kvm.git, and VirtualBox.svn, among other
open source projects. I'm finding a conflict between kvm.git and
VirtualBox.svn over the version of my linux kernel headers.
Specifically, kvm wants the files asm/kvm_para.h (and friends), but
apparently looks in /usr/include/asm for those files and can't find
them --> because my linux distro installs kernel headers from 2.6.26
in /usr/include/linux and /usr/include/asm.
If I make /usr/include/linux and /usr/include/asm symlinks to my
Linus.git repository, then kvm is happy and I'm happy -- until I
try to build VirtualBox.svn, which is now broken because of those
very same symlinks.
Because kvm is very fussy about using exactly the correct version
of the linux kernel headers, wouldn't it be reasonable to teach
kvm.git to look in the right place for those headers instead of in
/usr/include? I.e. /lib/modules/2.6.28-rc3/build/ for example.
Is there an easier way to fix this problem?
Thanks!
next reply other threads:[~2008-11-09 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 0:36 walt [this message]
2008-11-11 0:24 ` Preventing conflicts between kernel header versions? walt
2008-11-11 2:00 ` Glauber Costa
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='gf5bac$frp$1@ger.gmane.org' \
--to=w41ter@gmail.com \
--cc=kvm@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