Problem with default manifest when application provides its own

Christopher Faylor
Wed Apr 9 16:46:00 GMT 2014

On Wed, Apr 09, 2014 at 11:24:03AM -0400, Ken Brown wrote:
>I don't know if this report belongs here or if I should report a 
>binutils bug, but I'll start here.
>When building emacs-w32.exe with the current binutils, I end up with an 
>executable that won't run after it's stripped (at least on x86_64).  I 
>traced this to the fact that emacs-w32 comes with its own manifest.  My 
>understanding is that the emacs-w32 manifest should take precedence over 
>the Cygwin default manifest, but something's going wrong in this case.
>Here's a simple test case to illustrate the problem, using a slight 
>modification of the resource file that comes with emacs, and the 
>corresponding manifest (see attached).

Yes, this is definitely a binutils bug.  Would you mind filing a bug
report at:



Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list