[gcc] ar and runlib report "plugin needed to handle lto object"

[h-c-mueller]

Description / Steps to reproduce the issue

I assume the above noted issue is caused by a missing BFD-plugin.
Once I did
cp /usr/lib/gcc/x86_64-pc-cygwin/15.2.0/msys-lto_plugin.dll /usr/lib/bfd-plugins/
the problem was gone.
So I assume this step is missing during installation, maybe because it's typically a link.

Expected behavior

The plugin should be found by GNU binutils, e.g. ar, runlib etc.

Actual behavior

gcc output:

ar: libtest.o: plugin needed to handle lto object
ranlib: .libs/libtest.a(libtest.o): plugin needed to handle lto object

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MSYS_NT-10.0-19045

Are you willing to submit a PR?

No response

[lazka]

We do something similar for the MINGW version as you suggested: https://github.com/msys2/MINGW-packages/blob/280d56b3af12b24918099a986674e19f23cb9326/mingw-w64-gcc/PKGBUILD#L414-L416

[lazka]

Do you have a minimal reproducer by any chance?

[h-c-mueller]

I can reproduce the issue with the following script:

#!/bin/bash

rm -f test.c test.o libtest.a

cat > test.c << 'EOC'
int test_func(int x) { return x * x; }
EOC
    
gcc -flto -c test.c -o test.o
ar rcs libtest.a test.o
ranlib libtest.a