From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: lrn1986@gmail.com, gdb-patches@sourceware.org
Subject: Re: Fix compilation using mingw.org's MinGW
Date: Tue, 30 Apr 2019 17:17:00 -0000 [thread overview]
Message-ID: <83v9yvquoz.fsf@gnu.org> (raw)
In-Reply-To: <014135c5-5bb8-d451-ec7a-6d765b1ea5f5@redhat.com> (message from Pedro Alves on Tue, 30 Apr 2019 18:03:57 +0100)
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 30 Apr 2019 18:03:57 +0100
>
> The issue is where is that default set?
On some internal header file (it differs between various flavors of
MinGW). But no matter where it is set, it must be defined after _any_
standard header is included, so in practice I think it's defined at
the place where the patch tests for it.
In any case, the only platform which really needs this is mingw.org's
MinGW, where I actually tested this assumption. The other two,
MinGW64 and Cygwin, don't support older platforms (they actually don't
support XP anymore, only Vista and onward), so their default values
are higher than 0x0501 anyway.
next prev parent reply other threads:[~2019-04-30 17:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 15:36 Eli Zaretskii
2019-04-18 17:01 ` Kevin Buettner
2019-04-18 18:54 ` Eli Zaretskii
2019-04-18 20:38 ` Kevin Buettner
2019-04-19 6:19 ` Eli Zaretskii
2019-04-18 17:20 ` Pedro Alves
2019-04-18 17:22 ` Pedro Alves
2019-04-18 18:57 ` Eli Zaretskii
2019-04-19 10:51 ` Pedro Alves
2019-04-19 11:23 ` Eli Zaretskii
2019-04-19 11:33 ` Pedro Alves
2019-04-28 14:33 ` Eli Zaretskii
2019-04-30 12:56 ` Pedro Alves
2019-04-30 13:06 ` LRN
2019-04-30 15:25 ` Eli Zaretskii
2019-04-30 17:04 ` Pedro Alves
2019-04-30 17:17 ` Eli Zaretskii [this message]
2019-04-30 17:26 ` Pedro Alves
2019-04-30 17:40 ` Eli Zaretskii
2019-04-30 17:58 ` Pedro Alves
2019-04-30 18:34 ` Eli Zaretskii
2019-04-30 18:38 ` Pedro Alves
2019-04-30 17:50 ` LRN
2019-04-30 13:10 ` Pedro Alves
2019-04-30 15:23 ` Eli Zaretskii
2019-04-30 16:31 ` Pedro Alves
2019-05-03 8:04 ` Eli Zaretskii
2019-05-03 8:26 ` Eli Zaretskii
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=83v9yvquoz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.com \
--cc=palves@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).