qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/9] qemu-ga patch queue for 2.6
Date: Fri, 26 Feb 2016 11:39:01 +0000	[thread overview]
Message-ID: <CAFEAcA9Zt3yu7nKmdiWWiDiKyaHDAFv3EJDXKsSukn5W6jTJMw@mail.gmail.com> (raw)
In-Reply-To: <56CFE621.8040102@weilnetz.de>

On 26 February 2016 at 05:44, Stefan Weil <sw@weilnetz.de> wrote:
> Am 25.02.2016 um 22:27 schrieb Michael Roth:
>> Quoting Peter Maydell (2016-02-25 12:18:17)
> [...]
>>> I'm open to the idea of dropping old-mingw from the build rotation
>>> if it looks like it really is just totally hopeless, since I have
>>> a newer setup for it now.
>>
>> I wouldn't want to speak for dropping old mingw checks in general (cc'ing
>> Stefan), but for qemu-ga I think it makes sense. VSS/fsfreeze also
>> relies on mingw-w64 so it's really the only build system I use for
>> testing functionality.
>
> I cannot remember the last time when I used MinGW and don't think
> that it would produce a working program (wasn't there missing support
> for thread local storage?). Current Linux distributions include
> support for mingw-w64 cross compilations, but not for MinGW.
> And finally MinGW only supports 32 bit Windows which looses
> importance nowadays.
>
> Therefore dropping MinGW support and only supporting mingw-w64 would
> be fine for me.

OK, I have dropped my ancient mingw w32 setup from the compile
testing list, so this pull req is ok to apply as-is.

(This will also mean we no longer get annoying "failed to build"
issues for other gcc-4.2-isms like duplicate typedefs, missing
U or ULL suffixes, etc. Which is good I guess :-))

thanks
-- PMM

  reply	other threads:[~2016-02-26 11:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 17:11 [Qemu-devel] [PULL 0/9] qemu-ga patch queue for 2.6 Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 1/9] qga: Support enum names in guest-file-seek Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 2/9] qemu-ga: Fixed minor version switch issue Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 3/9] qga: implement the guest-get-vcpus for windows Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 4/9] qga: use more idiomatic qemu-style eol operators Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 5/9] qga: use size_t for wcslen() return value Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 6/9] qga: use wide-chars constants for wchar_t comparisons Michael Roth
2016-02-25 17:11 ` [Qemu-devel] [PULL 7/9] qga: fix off-by-one length check Michael Roth
2016-02-25 17:12 ` [Qemu-devel] [PULL 8/9] qga: check utf8-to-utf16 conversion Michael Roth
2016-02-25 17:12 ` [Qemu-devel] [PULL 9/9] qga: fix w32 breakage due to missing osdep.h includes Michael Roth
2016-02-25 18:18 ` [Qemu-devel] [PULL 0/9] qemu-ga patch queue for 2.6 Peter Maydell
2016-02-25 21:27   ` Michael Roth
2016-02-26  5:44     ` Stefan Weil
2016-02-26 11:39       ` Peter Maydell [this message]
2016-02-26 11:40         ` Peter Maydell

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=CAFEAcA9Zt3yu7nKmdiWWiDiKyaHDAFv3EJDXKsSukn5W6jTJMw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@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).