From: Alon Levy <alevy@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: yhalperi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC
Date: Thu, 9 Aug 2012 17:18:15 +0300 [thread overview]
Message-ID: <20120809141815.GC6680@garlic.redhat.com> (raw)
In-Reply-To: <5023C014.2080407@redhat.com>
On Thu, Aug 09, 2012 at 03:50:12PM +0200, Gerd Hoffmann wrote:
> On 08/09/12 15:41, Alon Levy wrote:
> > On Mon, Aug 06, 2012 at 09:31:19AM +0200, Gerd Hoffmann wrote:
> >>> diff --git a/configure b/configure
> >>> index cef0a71..5fcd315 100755
> >>> --- a/configure
> >>> +++ b/configure
> >>> @@ -2630,7 +2630,7 @@ EOF
> >>> spice_cflags=$($pkg_config --cflags spice-protocol spice-server 2>/dev/null)
> >>> spice_libs=$($pkg_config --libs spice-protocol spice-server 2>/dev/null)
> >>> if $pkg_config --atleast-version=0.8.2 spice-server >/dev/null 2>&1 && \
> >>> - $pkg_config --atleast-version=0.8.1 spice-protocol > /dev/null 2>&1 && \
> >>> + $pkg_config --atleast-version=0.12.0 spice-protocol > /dev/null 2>&1 && \
> >>
> >> I'd prefer to not require cutting-edge spice bits to build ...
> >
> > I only increased the protocol requirement, not the server.
>
> Distros tend to update those in sync, so this doesn't help much for the
> average user, this change would likely cause spice detection fail on
> almost every released distro ...
You're right. This would be solved with a submodule.
>
> > Meanwhile I'll add a define based on the pkg-config spice-protocol
> > version, which I can test from hw/qxl.c, since the commit adding
> > QXL_IO_MONITORS_CONFIG_ASYNC didn't introduce any new define I can
> > check.
>
> Just checking "SPICE_SERVER_VERSION >= 0x000b01" doesn't work? I'd
> expect spice-server 0.11.1+ having a dependency on a recent enougth
> spice-protocol so you can expect QXL_IO_MONITORS_CONFIG_ASYNC being
> present then, no?
Since spice-server now uses submodules, it doesn't check for an external
spice-protocol, so no.
>
> thanks,
> Gerd
>
next prev parent reply other threads:[~2012-08-09 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 13:08 [Qemu-devel] [PATCH 1/2] qxl: disallow unknown revisions Alon Levy
2012-07-23 13:08 ` [Qemu-devel] [PATCH 2/2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC Alon Levy
2012-07-23 16:33 ` [Qemu-devel] [PATCH v2] " Alon Levy
2012-07-25 9:00 ` Yonit Halperin
2012-07-25 17:29 ` Alon Levy
2012-07-26 5:26 ` Yonit Halperin
2012-07-28 8:56 ` Alon Levy
2012-07-28 9:01 ` Blue Swirl
2012-07-28 10:20 ` Alon Levy
2012-07-28 10:23 ` [Qemu-devel] [PATCH v3] " Alon Levy
2012-08-06 7:31 ` Gerd Hoffmann
2012-08-09 13:41 ` Alon Levy
2012-08-09 13:50 ` Gerd Hoffmann
2012-08-09 14:18 ` Alon Levy [this message]
2012-08-09 14:21 ` [Qemu-devel] [PATCH v4 1/2] " Alon Levy
2012-08-09 14:21 ` [Qemu-devel] [PATCH v4 2/2] configure: print spice-protocol and spice-server versions Alon Levy
2012-08-15 8:23 ` [Qemu-devel] [PATCH v4 1/2] qxl: add QXL_IO_MONITORS_CONFIG_ASYNC Gerd Hoffmann
2012-08-15 10:32 ` Alon Levy
2012-08-15 10:43 ` Gerd Hoffmann
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=20120809141815.GC6680@garlic.redhat.com \
--to=alevy@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).