[Bug target/69880] Linking Windows resource + implicit 'default-manifest.o' creates bad .exe

[boris at kolpackov dot net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69880

Boris Kolpackov <boris at kolpackov dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |boris at kolpackov dot net

--- Comment #1 from Boris Kolpackov <boris at kolpackov dot net> ---
Could this be the same merging issue as discussed here:

https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01386.html

BTW, looking at the patch, I initially thought that one workaround would be to
specify a directory (with -L) that contains a custom default-manifest.o so that
it is found before the system one. This, however, does not work since GCC
searches for it itself and only in its own library search paths (i.e.,
collect2.exe is already passed the absolute path).

Which suggests one possible way to support disabling this functionality: change
default-manifest.o to libdefault-manifest.a and use the standard
-ldefault-manifest logic to link it. This way the user will be able to provide
their own (potentially empty) version.