From: Mark McLoughlin <markmc@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Lalancette <clalance@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH] configure: make default KVM_VERSION qemu-kvm-devel
Date: Mon, 10 Aug 2009 10:39:22 +0100 [thread overview]
Message-ID: <1249897162.8784.66.camel@blaa> (raw)
In-Reply-To: <1249895994.8784.47.camel@blaa>
Released versions of qemu-kvm now have a KVM_VERSION of either
qemu-kvm-x.y.z or qemu-kvm-devel-XX. However, when building from git,
KVM_VERSION is kvm-devel.
Defaulting to qemu-kvm-devel makes more sense.
With newer versions of qemu-kvm, libvirt actually ignores the kvm
snapshot number (i.e. 86, 87 etc.) and just uses the 'qemu-kvm-'
string to detect that this is the kvm fork of qemu. The actual kvm
snapshot number is no longer important, it's the qemu version number
which is important.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
---
configure | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure b/configure
index 62028ca..cf8c4e6 100755
--- a/configure
+++ b/configure
@@ -166,7 +166,7 @@ kvm_version() {
if test -f "$fname"; then
cat "$fname"
else
- echo "kvm-devel"
+ echo "qemu-kvm-devel"
fi
}
--
1.6.2.5
next prev parent reply other threads:[~2009-08-10 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:31 [PATCH]: Always use KVM_VERSION to build version number Chris Lalancette
2009-08-09 9:58 ` Avi Kivity
2009-08-10 9:19 ` Mark McLoughlin
2009-08-10 9:39 ` Mark McLoughlin [this message]
2009-08-10 9:47 ` [PATCH] configure: make default KVM_VERSION qemu-kvm-devel Avi Kivity
2009-08-10 9:46 ` [PATCH]: Always use KVM_VERSION to build version number Avi Kivity
2009-08-10 9:52 ` Mark McLoughlin
2009-08-10 10:12 ` 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=1249897162.8784.66.camel@blaa \
--to=markmc@redhat.com \
--cc=avi@redhat.com \
--cc=clalance@redhat.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