From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pbonzini@redhat.com,
John Snow <jsnow@redhat.com>,
imammedo@redhat.com
Subject: [Qemu-devel] [PATCH 1/2] configure: require glib 2.22
Date: Tue, 12 May 2015 18:18:59 -0400 [thread overview]
Message-ID: <1431469140-22208-2-git-send-email-jsnow@redhat.com> (raw)
In-Reply-To: <1431469140-22208-1-git-send-email-jsnow@redhat.com>
This provides g_ptr_array_new_with_free_func, as well as a few
other functions that we've been hacking around in glib-compat.h.
Cleaning up the compatibility headers will come later.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
---
configure | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/configure b/configure
index 1f0f485..0c86eb2 100755
--- a/configure
+++ b/configure
@@ -2773,12 +2773,7 @@ fi
##########################################
# glib support probe
-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
-fi
+glib_req_ver=2.22
glib_modules=gthread-2.0
if test "$modules" = yes; then
glib_modules="$glib_modules gmodule-2.0"
--
2.1.0
next prev parent reply other threads:[~2015-05-12 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 22:18 [Qemu-devel] [PATCH 0/2] configure: increase glib requirement to 2.22 John Snow
2015-05-12 22:18 ` John Snow [this message]
2015-05-22 7:04 ` [Qemu-devel] [PATCH 1/2] configure: require glib 2.22 Alex Bennée
2015-05-12 22:19 ` [Qemu-devel] [PATCH 2/2] glib: remove stale compat functions John Snow
2015-05-22 7:05 ` Alex Bennée
2015-05-13 7:18 ` [Qemu-devel] [PATCH 0/2] configure: increase glib requirement to 2.22 Markus Armbruster
2015-05-13 9:33 ` Paolo Bonzini
2015-05-21 18:17 ` John Snow
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=1431469140-22208-2-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=imammedo@redhat.com \
--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 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).