All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] tests: use g_test_trap_fork for glib between 2.16 and 2.38
Date: Tue, 16 Sep 2014 18:33:52 +0200	[thread overview]
Message-ID: <54186670.1010604@redhat.com> (raw)
In-Reply-To: <CAFEAcA8pusT_BWe8zqJGET76V2dXvo7VQuu6M97sxPorpaXAog@mail.gmail.com>

Il 16/09/2014 18:28, Peter Maydell ha scritto:
>> > Though you would just drop support for "make check" on RHEL5.  Even
>> > "make -k check" would roughly work.
> Can't we just put in the makefile and configure magic to skip
> the test if the glib version is too old for it?

Yes, that's what Michael did (minus the magic to use the older
fork-based code).  But is it really worthwhile to support RHEL5?  We
made glib mandatory in 2011 (around RHEL6.2), and that broke RHEL4.  By
the time the next QEMU release is ready RHEL7.1 should be out, give or
take a month or so.

Paolo

  reply	other threads:[~2014-09-16 16:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 15:43 [Qemu-devel] [RFC PATCH] tests: use g_test_trap_fork for glib between 2.16 and 2.38 Paolo Bonzini
2014-09-16 16:18 ` Michael S. Tsirkin
2014-09-16 16:20 ` Peter Maydell
2014-09-16 16:23   ` Paolo Bonzini
2014-09-16 16:28     ` Peter Maydell
2014-09-16 16:33       ` Paolo Bonzini [this message]
2014-09-16 16:45         ` Peter Maydell
2014-09-16 16:57           ` Michael S. Tsirkin
2014-09-16 17:23             ` Peter Maydell
2014-09-16 17:54               ` Michael S. Tsirkin
2014-09-16 16:43       ` Michael S. Tsirkin
2014-09-16 16:42     ` Michael S. Tsirkin

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=54186670.1010604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mst@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.