From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: sizious@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH][PR build/23568] Fix gdb-7.12.1 MinGW/MSYS build issue
Date: Tue, 28 Aug 2018 17:22:00 -0000 [thread overview]
Message-ID: <83wosa2yos.fsf@gnu.org> (raw)
In-Reply-To: <18eaf339-ca0a-061c-4a17-b837e6ef81a2@redhat.com> (message from Pedro Alves on Tue, 28 Aug 2018 17:57:43 +0100)
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 28 Aug 2018 17:57:43 +0100
>
> On 08/28/2018 01:01 PM, SiZiOUS wrote:
> > This little patch was made to allow the compilation under the MinGW/MSYS legacy environment (I don't know for the newer MinGW-w64/MSYS2 environment!).
> > If this patch is not applied, then the compilation of gdb-7.12.1 under MinGW/MSYS is impossible.
>
> GDB 7.12 is old by now and not actively maintained.
>
> Can you check whether this is necessary on the master branch?
AFAICS, we include winerror.h via serial.h, which includes winsock2.h,
which includes winerror.h. Older MinGW included that via the chain
windows.h->windef.h->winnt.h.
SiZiOUS, what version of the MinGW runtime are you using?
next prev parent reply other threads:[~2018-08-28 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 12:01 SiZiOUS
2018-08-28 16:57 ` Pedro Alves
2018-08-28 17:22 ` Eli Zaretskii [this message]
2018-08-28 22:19 ` SiZiOUS
2018-08-29 8:04 ` SiZiOUS
2018-09-09 20:06 ` Eli Zaretskii
[not found] ` <ddb12e03-7fc3-bf4b-cd24-235b43c33d38@gmail.com>
2018-12-02 13:52 ` SiZiOUS
2018-08-29 15:50 ` Simon Marchi
2018-08-29 16:19 ` Eli Zaretskii
2018-08-29 16:25 ` Tom Tromey
2018-08-29 17:01 ` SiZiOUS
2018-08-29 17:46 ` Pedro Alves
2018-08-29 16:59 ` SiZiOUS
2018-08-29 18:27 ` Pedro Alves
2018-08-29 21:07 ` SiZiOUS
2018-08-29 17:54 ` Pedro Alves
2018-08-29 18:09 ` 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=83wosa2yos.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sizious@gmail.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