Comment # 3 on bug 1201107 from Ralf Habacker

Created attachment 859970 [details]
build log for gcc12 and binutils 2.33

The issue does not occur with gcc12 and binutils 2.33 as shown from the
appended log: 

[  168s] extracting debug info from
/home/abuild/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin/liborcus-0.11-0.dll
[  169s]
/home/abuild/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-0.11-0.dll/E096C2548BBFFFDDD7E5D34E31C2D1FB1/liborcus-0.11-0.dll.sym
[  169s]
~/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin
~/rpmbuild/BUILD/liborcus-0.11.2
[  170s] ~/rpmbuild/BUILD/liborcus-0.11.2
[  170s] extracting debug info from
/home/abuild/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin/liborcus-mso-0.11-0.dll
[  170s]
/home/abuild/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-mso-0.11-0.dll/18938F56640FA9AEF22D594A52397CF21/liborcus-mso-0.11-0.dll.sym

which makes me suspect that the update to mingw32-binutils-2.38 is responsible
for this problem and needs to be fixed there.