From: Pedro Alves <palves@redhat.com>
To: SiZiOUS <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 16:57:00 -0000 [thread overview]
Message-ID: <18eaf339-ca0a-061c-4a17-b837e6ef81a2@redhat.com> (raw)
In-Reply-To: <56c5911c-e0ba-5a17-64bb-3634af60a07d@gmail.com>
Hi,
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?
Also, it's a bit curious that nobody else ran into this so far. Could it
be you're using an older mingw and that the issue has been fixed in the
mingw/w32api headers meanwhile?
> This fix is not intrusive as it's taken into account only if ERROR_IO_PENDING is not declared in the current scope, so it should be considered safe.
> See the Bugzilla bug entry for more details.
>
> Please note, this fix only allows the build possible under MinGW/MSYS, there is no bug fixes or improvements for GDB itself.
>
> gdb/ChangeLog:
> 2018-08-28Â SiZiOUS<sizious@gmail.com>
>
> Â Â Â Â PR build/23568
> Â Â Â Â * ser-mingw.c: Conditioned fix allowing compilation under
> Â Â Â Â the MinGW/MSYS legacy environment ('ERROR_IO_PENDING' was not
> Â Â Â Â declared in the scope).
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-08-28 16:57 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 [this message]
2018-08-28 17:22 ` Eli Zaretskii
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=18eaf339-ca0a-061c-4a17-b837e6ef81a2@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--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