[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe
boris at kolpackov dot net
gcc-bugzilla@gcc.gnu.org
Mon Jul 11 15:36:00 GMT 2016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880
--- Comment #3 from Boris Kolpackov <boris at kolpackov dot net> ---
Ok, I've added support for embedding custom manifests in build2. The resulting
.exe's work as expected: custom manifest is used instead of (or in addition to)
the default one. However, with grep I can still see both manifests being
present in the executable (which seems to be the problem the original reporter
is experiencing).
ld --version
GNU ld (GNU Binutils) 2.25.1
I see this is not the latest generally, but it is the latest available from the
MSYS2 repositories. The last commit here says 2.26 is still no usable:
https://github.com/Alexpux/MSYS2-packages/tree/master/binutils
Does it still make sense to file a binutils bug report?
More information about the Gcc-bugs
mailing list