From: Chris Johns <chrisj@rtems.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: use glib in glib pkg-config check.
Date: Wed, 05 Feb 2014 16:31:12 +1100 [thread overview]
Message-ID: <52F1CCA0.2030708@rtems.org> (raw)
In-Reply-To: <20140204095918.GA4393@redhat.com>
On 4/02/2014 8:59 pm, Daniel P. Berrange wrote:
>
> On Linux there are more flags present in gthread-2.0.pc that are not
> present in glib-2.0.pc:
>
> Name: GThread
> Description: Thread support for GLib
> Requires: glib-2.0
> Version: 2.38.2
> Libs: -L${libdir} -lgthread-2.0 -pthread
> Cflags: -pthread
>
>
> The 'Requires: glib-2.0' line there means that when QEMU asking for
> flags for 'gthread-2.0', it will *also* get any flags listed in the
> 'glib-2.0.pc' file.
>
Ah yes this is correct. I will take a closer look. Thanks for this.
>>>
>>> What glib version are you seeing a problem with ?
>>
>> glib-2.39.3 on darwin 13.0.2 (Mavrick).
>>
>>> It seems we should
>>> really fix glib, since this will affect countless 1000's of apps using
>>> it, not try to workaround in all downstream apps.
>>
>> This is outside of my field of view; to me it still looks qemu specific.
>
> I don't believe so. What QEMU is currently doing is correct so I
> believe this is either a darwin specific glib bug or a flawed
> build of glib on darwin.
>
Yes I agree.
Chris
prev parent reply other threads:[~2014-02-05 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 4:26 [Qemu-devel] [PATCH] configure: use glib in glib pkg-config check Chris Johns
2014-02-03 10:29 ` Daniel P. Berrange
2014-02-03 22:56 ` Chris Johns
2014-02-03 23:17 ` Peter Maydell
2014-02-04 9:59 ` Daniel P. Berrange
2014-02-05 5:31 ` Chris Johns [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=52F1CCA0.2030708@rtems.org \
--to=chrisj@rtems.org \
--cc=berrange@redhat.com \
--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.