From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>
Cc: Tom Musta <tommusta@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Build Broken?
Date: Tue, 13 May 2014 18:14:08 +0200 [thread overview]
Message-ID: <537244D0.7010707@redhat.com> (raw)
In-Reply-To: <CAFEAcA8+M1bFn9kKnUJHarKd8tY+vZOzRN0v2Eth0MC+=drCjw@mail.gmail.com>
Il 13/05/2014 17:55, Peter Maydell ha scritto:
> On 13 May 2014 16:34, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> 13.05.2014 18:17, Tom Musta wrote:
>>> The current origin/master is not building for me:
>>>
>>> LINK qemu-img
>>> qemu-img.o: In function `add_format_to_seq':
>>> /bghome/tmusta/powerisa/qemu/qemu/qemu-img.c:73: undefined reference to `g_sequence_lookup'
>>> collect2: ld returned 1 exit status
>>> make: *** [qemu-img] Error 1
>> []
>>> It appears that this code is dependent on glib.h function that is newer than one of my build systems
>>> (RHEL 6 update 5, gcc version 4.4.7 20120313 (Red Hat 4.4.7-4))
>>>
>>> Is this a known limitation? i.e. is QEMU 2.1 going to prereq a newer version of glib2?
>>
>> If we're going to require more recent glib (g_sequence_lookup() first appeared in 2.26),
>> let's require at least 2.31 with the new threading primitives as well.
>
> This is the wrong end to approach this question from, I think.
> We should start with "which RedHat/Fedora/Debian/SuSE/etc
> distro versions do we need to support?" and then can derive
> the minimum glib version from that.
>
> In particular, if RHEL6 doesn't have a glib with
> g_sequence_lookup I think it's a fairly straightforward
> decision to say we can't use it.
I think we should stick for RHEL5's 2.12 for a few months still, at
least until RHEL7.0 or 7.1 comes out. Looks like SLES's 2.22 will be
the next lowest target.
Paolo
prev parent reply other threads:[~2014-05-13 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:17 [Qemu-devel] Build Broken? Tom Musta
2014-05-13 15:34 ` Michael Tokarev
2014-05-13 15:53 ` Cornelia Huck
2014-05-13 15:55 ` Peter Maydell
2014-05-13 15:58 ` Tom Musta
2014-05-13 16:14 ` Paolo Bonzini [this message]
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=537244D0.7010707@redhat.com \
--to=pbonzini@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tommusta@gmail.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).