From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: kvm@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>,
Weidong Han <weidong.han@intel.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: Build breakage between kvm-userspace.git HEAD and 2.6.29-rc8
Date: Sun, 15 Mar 2009 11:23:32 +0200 [thread overview]
Message-ID: <49BCC914.4070204@redhat.com> (raw)
In-Reply-To: <49BA7D77.1010003@gmail.com>
Gregory Haskins wrote:
> Hi kvm-devs,
> Been away from the kvm scene for a while...hope everyone is well.
>
> FYI: There are a few build breakages between kvm-userspace.git HEAD
> (f29d402ab885d30bfa7350378cff911c9c17a226) when you compile against
> Linus' linux-2.6.git HEAD
> (v2.6.29-rc8-041b62374c7fedc11a8a1eeda2868612d3d1436c)
>
> I am not sure if this is a supported configuration (e.g. perhaps you
> only support building kvm-userspace HEAD against Avi's kernel tree?).
> But in case this was unintentional, read on...
>
It's a semi-supported configuration. We don't test it, but we'll fix
reported bugs (or apply patches...).
> First error:
>
> libkvm.c:702: error: ‘struct kvm_irq_level’ has no member named ‘status’
> make[1]: *** [libkvm.o] Error 1
>
> Which is attributable to:
>
> commit ea1b668e7684dc43e9d198ba0b25fe47a0b2acd2
> Author: Gleb Natapov <gleb@redhat.com>
> Date: Wed Feb 4 17:30:01 2009 +0200
>
> kvm: qemu: handle IRQ status injection in userspace
>
This is due to a missing #ifdef KVM_CAP_... somewhere.
Gleb, can you take a look?
[more breakage]
Let's take this one at a time.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-15 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:36 Build breakage between kvm-userspace.git HEAD and 2.6.29-rc8 Gregory Haskins
2009-03-15 9:23 ` Avi Kivity [this message]
2009-03-15 10:19 ` Gleb Natapov
2009-03-15 10:43 ` Avi Kivity
2009-03-15 10:42 ` Gleb Natapov
2009-03-15 12:19 ` Avi Kivity
2009-03-16 9:25 ` Han, Weidong
2009-03-16 9:48 ` Avi Kivity
2009-03-17 1:02 ` Han, Weidong
2009-03-17 9:36 ` Avi Kivity
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=49BCC914.4070204@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=weidong.han@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.