From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] pci: Fix compiler warning (MinGW-w64 gcc 4.9)
Date: Fri, 15 May 2015 10:20:23 -0600 [thread overview]
Message-ID: <55561CC7.10404@redhat.com> (raw)
In-Reply-To: <87y4kqnuc2.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On 05/15/2015 02:00 AM, Markus Armbruster wrote:
> Stefan Weil <sw@weilnetz.de> writes:
>
>> i686-w64-mingw32-gcc 4.9.1 from Debian Jessie complains:
>>
>
> This is obviously a bug in that version of MinGW. Have you reported it?
I don't know if Debian has a bug filed against mingw yet, but I
mentioned elsewhere in the thread that I filed a bug for Fedora which is
also impacted.
> Do we really want to work around it?
That, I'm not sure. It takes a while for updated mingw headers to
propagate, and the fix is small enough that it won't hurt to leave the
fix in place even after updated headers are available. But since the
problem is a missing attribute in the header causing a compiler warning,
it could be worked around by turning off compiler warnings until a new
header is present.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-05-15 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 20:38 [Qemu-devel] [PATCH] pci: Fix compiler warning (MinGW-w64 gcc 4.9) Stefan Weil
2015-05-14 21:06 ` Eric Blake
2015-05-14 21:16 ` Eric Blake
2015-05-14 21:22 ` Eric Blake
2015-05-14 21:30 ` Eric Blake
2015-05-15 8:00 ` Markus Armbruster
2015-05-15 16:20 ` Eric Blake [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=55561CC7.10404@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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).