Binutils causes abnormally large, non-working binaries since 2.43

[Jan Beulich]

On 07.03.2025 22:40, Bastiaan Timmer wrote:
> Thank you for taking the time to look into this further.
> 
> Looking at the PKGBUILD (a small configuration file, that is used on 
> Arch Linux to build packages), I see the packaging-step runs:
> 
>       find "${pkgdir}/usr/${_arch}" -name '*.exe' -exec ${_arch}-strip {} \;
>       find "${pkgdir}/usr/${_arch}" -name '*.dll' -exec ${_arch}-strip 
> --strip-unneeded {} \;
>       find "${pkgdir}/usr/${_arch}" -name '*.a' -o -name '*.dll' | xargs 
> ${_arch}-strip -g
> 
> Where `${_arch}-strip' would expand to 'x86_64-w64-mingw32-strip' (or 
> similar for i686). Would that explain the apparent use of objcopy?

Yes. Question is: Why are these not visible in the build logs you provided?

> I have built two versions of mingw-w64-openssl, one with the upstream 
> 2.44 version of binutils (I had only tried up until 2.43 before), and 
> one with version 2.44 with your patch applied. I am happy to report your 
> tiny patch also appears to solve the issues. The size of the openssl 
> libraries is back to normal when compiled with 2.44_patched, and 
> binaries linked to these openssl libraries successfully run on Windows.
> 
> I have opened a bug about this issue about two weeks ago (here: 
> https://sourceware.org/bugzilla/show_bug.cgi?id=32732). I assume this 
> info is useful there, maybe you want to chime in? Or, of course, I'd be 
> happy to report these latest findings myself if you prefer.

Indeed, I thought it's better to comment there.

Jan