From: Christian Biesinger <cbiesinger@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Building today's snapshot of GDB with MinGW
Date: Tue, 30 Jun 2020 13:21:44 -0500 [thread overview]
Message-ID: <CAPTJ0XED1q6imNeXO73RJBJtmr4Xjm60gRoYhNT39NRxv7UTgg@mail.gmail.com> (raw)
In-Reply-To: <83ftaczfvl.fsf@gnu.org>
On Tue, Jun 30, 2020 at 11:18 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Mon, 29 Jun 2020 21:27:32 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > At Joel's request I've built today's (29 June) snapshot of GDB using
> > mingw.org's MinGW and GCC 9.2.0. There are a few issues I bumped into
> > related to Gnulib and MinGW runtime (which I recently upgraded to a
> > newer version), and I'm still working on those. So what's below is an
> > interim report of issues related to GDB itself:
>
> More information:
>
> Two issues I reported to Gnulib were fixed:
>
> https://lists.gnu.org/archive/html/bug-gnulib/2020-06/msg00068.html
> https://lists.gnu.org/archive/html/bug-gnulib/2020-06/msg00069.html
>
> So I hope we could update from Gnulib before the GDB 10 branch is cut.
I can make a patch for that.
> Another problem is specific to the MinGW headers, and was also fixed:
>
> https://osdn.net/projects/mingw/lists/archive/users/2020-June/000543.html
Better link, I think:
https://osdn.net/projects/mingw/lists/archive/users/2020-June/000548.html
"feel free to modify your local copy, and I'll revert that change for
future releases."
Christian
next prev parent reply other threads:[~2020-06-30 18:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 18:27 Eli Zaretskii
2020-06-29 20:36 ` Christian Biesinger
2020-06-30 14:09 ` Eli Zaretskii
2020-06-30 22:24 ` Simon Marchi
2020-07-01 15:09 ` Eli Zaretskii
2020-07-02 13:50 ` Eli Zaretskii
2020-07-02 14:25 ` Simon Marchi
2020-07-02 14:30 ` Simon Marchi
2020-07-02 17:47 ` Eli Zaretskii
2020-07-02 14:40 ` Pedro Alves
2020-07-02 17:46 ` Eli Zaretskii
2020-07-02 18:21 ` Pedro Alves
2020-07-02 18:33 ` Eli Zaretskii
2020-07-02 18:34 ` Pedro Alves
2020-07-01 15:20 ` Eli Zaretskii
2020-07-01 19:25 ` Christian Biesinger
2020-07-02 2:29 ` Eli Zaretskii
2020-07-02 10:18 ` Hannes Domani
2020-07-02 13:20 ` Eli Zaretskii
2020-07-06 10:39 ` Hannes Domani
2020-07-06 16:35 ` Eli Zaretskii
2020-07-01 19:25 ` Joel Brobecker
2020-07-02 13:46 ` Eli Zaretskii
2020-06-30 16:18 ` Eli Zaretskii
2020-06-30 18:21 ` Christian Biesinger [this message]
2020-06-30 18:28 ` Eli Zaretskii
2020-07-01 19:29 ` Joel Brobecker
2020-07-02 2:31 ` Eli Zaretskii
2020-07-01 19:30 ` Joel Brobecker
2020-07-02 13:39 ` Eli Zaretskii
2020-07-03 15:25 ` Joel Brobecker
2020-07-27 9:49 ` Tom de Vries
2020-07-27 10:05 ` Tom de Vries
2020-07-27 10:26 ` Tom de Vries
2020-07-27 11:48 ` [committed][gdb/build] Fix typo sys/sockets.h -> sys/socket.h Tom de Vries
2020-07-27 12:51 ` Joel Brobecker
2020-07-27 14:18 ` Building today's snapshot of GDB with MinGW Eli Zaretskii
2020-07-02 14:12 ` Eli Zaretskii
2020-07-03 15:08 ` 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=CAPTJ0XED1q6imNeXO73RJBJtmr4Xjm60gRoYhNT39NRxv7UTgg@mail.gmail.com \
--to=cbiesinger@google.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).