This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with default manifest when application provides its own
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 9 Apr 2014 12:46:25 -0400
- Subject: Re: Problem with default manifest when application provides its own
- Authentication-results: sourceware.org; auth=none
- References: <53456613 dot 4090307 at cornell dot edu>
- Reply-to: cygwin at cygwin dot com
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:
https://sourceware.org/bugzilla/enter_bug.cgi?product=binutils
?
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple