X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=MYoZvRAKES22yMmgIQyRqvQ46n5xZJZZtrZDHgZoOJI43o8xsh3/X
	YaJcdqWxbAxAnkuoXlisnDLZo5eeFtMl/wfTNGgo8/f/YEJzaicE06Ki4wZOWLWt
	L9oRrfpwQ5ShfRjhdHvuslbuHPx3CoC/qB62mnPfGNsY6AWI22mhAI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=gonZ/spF18Yrlsvccan9A388JeQ=; b=H2rcabycifTajVOKymSWNuoMPQIk
	mYctH9mrRYF86ipwfeQ4xUodeHvkyj9fpGv1bG7T8zKUz5LF3EmzuNWXaQfJ7pQB
	ZkfVQ8h8YBmSnp6n2PZ37nVexHMZ4LoaRlrObPgudxDGktmDKkTtS0BpmB5mcB2e
	PquT8TaOBz3Z7xs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/Vsrg1vm0TIUSBsT8JEymp
Date: Wed, 9 Apr 2014 12:46:25 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with default manifest when application provides its own
Message-ID: <20140409164625.GB5519@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <53456613 DOT 4090307 AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53456613.4090307@cornell.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)

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