From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix compilation using mingw.org's MinGW
Date: Fri, 19 Apr 2019 11:23:00 -0000 [thread overview]
Message-ID: <83d0lick7o.fsf@gnu.org> (raw)
In-Reply-To: <556cefd7-47ce-54ab-a228-2c727aab4179@redhat.com> (message from Pedro Alves on Fri, 19 Apr 2019 11:51:46 +0100)
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Fri, 19 Apr 2019 11:51:46 +0100
>
> building at all either. The subject for the commit that added that NEWS entry
> sound like that was the intention:
>
> commit 742a7df5f4a149f0818aaccfc432c4c0c9a6e26d
> Author: Eli Zaretskii <eliz@gnu.org>
> AuthorDate: Sat Mar 2 15:18:32 2019 +0200
>
> GDB no longer supports Windows before XP.
>
> But surprisingly, I can't find the discussion behind this commit
> in the archives to see the context and what was decided.
The discussion which led to that change is here:
https://www.sourceware.org/ml/gdb-patches/2019-02/msg00574.html
> >> So shouldn't we instead be setting _WIN32_WINNT to some
> >> appropriate number?
> >
> > I don't mind, but where?
>
> I'd do it in common/common-defs.h, before any #include, where we define
> other macros that must be defined before any include, like
> __STDC_LIMIT_MACROS, _FORTIFY_SOURCE, etc.
>
> > And also: should we make such changes on the
> > 8.3 branch at this time?
>
> Not sure. Off hand I'd think it's pretty safe, but maybe for 8.3
> your patch is safer.
I will try doing this in common-defs.h, but for the branch, we could
set _WIN32_WINNT only in windows-nat.c, as that's the only file that
currently cares, which should be safer. WDYT?
next prev parent reply other threads:[~2019-04-19 11:23 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 [this message]
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
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=83d0lick7o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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).