All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, mjt@tls.msk.ru, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] configure: bump glib version to 2.16
Date: Tue, 10 Mar 2015 13:40:36 -0400	[thread overview]
Message-ID: <54FF2C94.1090303@redhat.com> (raw)
In-Reply-To: <1426009047-25139-1-git-send-email-jsnow@redhat.com>

Adding in Michael Tokarev, I fat-fingered his email address.

On 03/10/2015 01:37 PM, John Snow wrote:
> Our qtest suite relies on many functions available only in glib 2.16+.
> Even though our base QEMU binary may only require 2.12+, it is confusing
> to have two separate version requirements.
>
> Thus, this is an attempt to re-establish a sane baseline for the entire
> project at 2.16+.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>   configure | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 7ba4bcb..c38506c 100755
> --- a/configure
> +++ b/configure
> @@ -2748,7 +2748,7 @@ if test "$mingw32" = yes; then
>       # g_poll is required in order to integrate with the glib main loop.
>       glib_req_ver=2.20
>   else
> -    glib_req_ver=2.12
> +    glib_req_ver=2.16
>   fi
>   glib_modules=gthread-2.0
>   if test "$modules" = yes; then
>

  reply	other threads:[~2015-03-10 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 17:37 [Qemu-devel] [PATCH] configure: bump glib version to 2.16 John Snow
2015-03-10 17:40 ` John Snow [this message]
2015-03-10 17:41 ` Peter Maydell
2015-03-10 17:43   ` John Snow
2015-03-10 17:45     ` Peter Maydell
2015-05-07 12:22       ` Peter Maydell
2015-05-07 15:12         ` John Snow
2015-05-08  6:15           ` Markus Armbruster

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=54FF2C94.1090303@redhat.com \
    --to=jsnow@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 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.