Commit: Update libiberty

[Christophe Lyon]

On 1/12/26 13:48, Jan Beulich wrote:
> On 12.01.2026 13:43, Nick Clifton wrote:
>> I would definitely like to switch to a newer version of autoconf.  But I do
>> not want to do it right before branching for a new release.  So I think that
>> for now:
>>
>>     1. We leave in H.J.'s patch - it fixes a real problem that prevents
>>        the binutils from being built with -fsanitize=address,undefined.
>>
>>     2. After the branch is made some kind soul offers to try out building
>>        the configure and makefiles with newer versions of the auto tools,
>>        and fixing any problems that arise.
>>
>> Or is this too controversial ?
> 
> Fine with me, fwiw. But see also the other email about builder fallout from
> (apparently) the update + re-patch.
> 
 > Jan

Sounds good to me too.

In addition, I was thinking I could post an updated version of my 
suggestion from April 2024:
https://sourceware.org/pipermail/binutils/2024-April/133731.html

FYI, on the GCC side, we have recently added a contrib/ci-containers 
sub-directory, with "autoregen" as its first member, which includes a 
copy of autoregen.py from Sourceware's bot.  The goal is to automate 
this check within the (still experimental) forge.

So I'd like to post a binutils / gdb patch to add contrib/ci-containers 
with the same contents as GCC currently.  Although binutils / gdb don't 
use the forge, it would help Sourceware's autoregen bot use a per-repo 
autoregen.py.

When binutils / gdb update their versions of autotools, we'll update 
their copy of autoregen.py, without having to worry about GCC's version, 
and still keep autoregen bots for both projects.

Thanks,

Christophe