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

[nickc at gcc dot gnu.org]

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

Nick Clifton <nickc at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at gcc dot gnu.org

--- Comment #2 from Nick Clifton <nickc at gcc dot gnu.org> ---
Hi Boris,

  Which version of the linker are you using ?  I ask because there have been
  several bugs reported with merging windows resources, but I think that these
  have all been fixed now.

> But, the way these two objects are linked also causes the second instance 
> to be apparently "orphaned" between two valid sections (.rsrc and .reloc 
> in my particular case) of the executable.

  If you are using the latest version of the linker and this is still happening
  then it would definitely seem to be a linker bug.  If so, it would be useful
  if you could report this on the binutils bugzilla system, and provide a test
  case that demonstrates the problem.


> 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.

  Personally I have no objections to this idea.  It would be nice however if
  one of the Cygwin maintainers could check it out and make sure that it does
  not stop default manifects from working in the way that they want.

Cheers
  Nick