https://sourceware.org/bugzilla/show_bug.cgi?id=16807
--- Comment #2 from Angelo Graziosi <angelo.graziosi at alice dot it> --- (In reply to Nick Clifton from comment #1) > Hi Corinna, > > I have started looking into this bug, but I am a bit stumped. :-( > > I guess that the problem is connected with the default manifest being > added in to the executable's resources. But looking at the decompiled > resources in the dlg_one.out executable everything looks fine. Then I > started to wonder. Maybe it is the fact that there are now *3* top > level entries in the resource Type table instead of 2. Maybe the > dlg_one.c application only expects there to be 2 entries and somehow it > is getting confused. Unfortunately I am not enough of a Window resource > expert to tell. But you are... So - is this a possibility ? Just for completeness, the workaround described here http://cygwin.com/ml/cygwin/2014-04/msg00134.html works for me. It seems to confirm that the origin of these issues is this defaul manifest in new binutils releases. Ciao, Angelo. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
