From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>, Joel Brobecker <brobecker@adacore.com>
Subject: Re: MinGW build of GDB 13 snapshot
Date: Mon, 19 Dec 2022 14:14:35 -0700 [thread overview]
Message-ID: <87len3ksec.fsf@tromey.com> (raw)
In-Reply-To: <83k02qgdbo.fsf@gnu.org> (Eli Zaretskii via Gdb-patches's message of "Sat, 17 Dec 2022 19:16:59 +0200")
>>>>> "Eli" == Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org> writes:
Eli> One of those issues is in the bfd directory, and I will report it to
Eli> the Binutils list. I'm asking here what to do with that issue
Eli> meanwhile: do I install a fix for it in our copy of bfd, or do I wait
Eli> for Binutils folks to fix it up-stream? The fix is simple:
IMO it's fine to put on the gdb 13 branch.
I suppose if binutils wants changes we can consider putting their
approved version on the branch instead.
Eli> The other issue is with the new stuff in nat/windows-nat.c. Here are
Eli> the compilation error messages:
...
Eli> This happens because these two symbols are not visible when compiling
Eli> GDB with _WIN32_WINNT set to an older version that Windows 8. The
Eli> patch for this is below. OK to commit it on the master branch?
This is ok. Thank you.
Tom
next prev parent reply other threads:[~2022-12-19 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 17:16 Eli Zaretskii
2022-12-19 21:14 ` Tom Tromey [this message]
2022-12-20 14:12 ` Eli Zaretskii
2022-12-21 3:26 ` Joel Brobecker
2022-12-22 10:46 ` Eli Zaretskii
2022-12-23 3:28 ` Joel Brobecker
2022-12-23 8:07 ` Eli Zaretskii
2022-12-23 9:13 ` Joel Brobecker
2022-12-23 11:21 ` 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=87len3ksec.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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).