From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [ANNOUNCEMENT] GDB 16.1 released!
Date: Wed, 22 Jan 2025 11:02:24 +0000 [thread overview]
Message-ID: <87o6zzm7r3.fsf@redhat.com> (raw)
In-Reply-To: <Z5Bj+rIAwhdcmHjQ@adacore.com>
Joel Brobecker <brobecker@adacore.com> writes:
> [Apologies for the resend, Andrew - wrong email address for the gdb
> mailing-list]
>
>> If/when this is merged I do plan to back-port this to the gdb-16-branch,
>> but given the build following the suggested steps works fine, I'm not
>> sure this justifies a follow up release. But I wanted to raise this for
>> discussion.
>
> I fear that using a relative path to configure when building out-of-tree
> might be fairly common. Thankfully, the workaround is relatively
> straightforward, so once users get the answer, they can move forward
> quickly, but getting this answer may not be straightforward.
>
> It might be worth doing a first corrective release right away.
The bfd fix was approved and merged to master. I have also pushed the
fix to the gdb-16-branch. If we did want a corrective fix then we have
everything we need in place.
Thanks,
Andrew
next prev parent reply other threads:[~2025-01-22 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 10:38 Joel Brobecker via Gdb-announce via Gdb
2025-01-21 13:55 ` Andrew Burgess via Gdb
[not found] ` <Z5BiYQ6L6bfNZy3M@adacore.com>
2025-01-22 3:20 ` Joel Brobecker via Gdb
2025-01-22 11:02 ` Andrew Burgess via Gdb [this message]
2025-01-22 11:07 ` Joel Brobecker via Gdb
2025-01-22 19:55 ` Andrew Burgess via Gdb
2025-01-22 21:22 ` Andrew Burgess via Gdb
2025-01-23 6:29 ` Joel Brobecker via Gdb
2025-01-28 13:04 ` Andrew Burgess via Gdb
2025-01-29 5:18 ` Joel Brobecker via Gdb
2025-01-23 18:05 ` Luis Machado via Gdb
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=87o6zzm7r3.fsf@redhat.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=brobecker@adacore.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