From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>,
brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: MinGW build of GDB 13 snapshot
Date: Wed, 21 Dec 2022 07:26:49 +0400 [thread overview]
Message-ID: <Y6J8+bbArR9aDOAM@adacore.com> (raw)
In-Reply-To: <83bknycgg3.fsf@gnu.org>
Hi Eli,
On Tue, Dec 20, 2022 at 04:12:12PM +0200, Eli Zaretskii wrote:
> > From: Tom Tromey <tom@tromey.com>
> > Cc: Eli Zaretskii <eliz@gnu.org>, Joel Brobecker <brobecker@adacore.com>
> > Date: Mon, 19 Dec 2022 14:14:35 -0700
> >
> > >>>>> "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.
>
> The problem is now fixed in upstream Binutils, see
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=29915
>
> So I think I will fix this on the gdb 13 branch only, and master will
> be fixed in due time when we import the latest BFD? Or do you want me
> to fix this on both branches? Joel?
Binutils and GDB share the same repository, so it's the same master
branch. Alan's fix on master, if you confirm fixes the problem on
master, can be cherry-picked to the gdb-13-branch.
Otherwise, if Alan's fix does not work, we can indeed start with
your patch in gdb-13-branch, and wait for master to get fixed
via the binutils team.
--
Joel
next prev parent reply other threads:[~2022-12-21 3:26 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
2022-12-20 14:12 ` Eli Zaretskii
2022-12-21 3:26 ` Joel Brobecker [this message]
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=Y6J8+bbArR9aDOAM@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).