On Apr 9 12:46, Christopher Faylor wrote: > 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
Not required, Angelo already created a report for this a couple of days ago: https://sourceware.org/bugzilla/show_bug.cgi?id=16807 Apparently there's still a bug when merging Windows resources. There's no fix for it yet. Perhaps we should revert to binutils 2.23.x for the time being, since there are a couple of problems in ld which still need fixing. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgplcu_hKxWKr.pgp
Description: PGP signature