[ANNOUNCEMENT] GDB 16.1 released!

[Luis Machado]

On 1/22/25 19:55, Andrew Burgess via Gdb wrote:
> Joel Brobecker <brobecker@adacore.com> writes:
> 
>>>>> 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.
>>
>> Great news!
>>
>> What's the general sentiment towards the corrective release?
>> Do people agree that it's worth the effort doing on now?
> 
> I don't want to impose unnecessary additional work on you, but my
> feeling is that a corrective release would be a good idea given that
> configuring using '../configure' isn't a totally crazy thing to do.
> 
> But would be nice to see what others think.
> 
> Thanks,
> Andrew
> 

I think it would be nice to have one, also to fix the x packet hiccup. Of
course, as long as that doesn't create substantial work for you on the
release.