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=iJ/hOxeeBvblu46cNJTC/BoIovUGppvE5FvrWTwYB7cQ13r6epRyN
	zTn/64uMBBJ1UVD1+9hkFmYsrylHfDseefJ6QCw3bFTcvVUdSioG951xNBfGvFJ6
	CP5exN+alWGlYuEuqAj14xjpX/EmY5ym3zfugJQj98nyBW0TO6ASos=
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=USuBxGqiQCnqDGLYGM/dCKBBIQU=; b=WMqLZIjnxJug4yUZxGkYBJftR50x
	mxBV2sHQmaiN2jOpYPkMlyl0uh+sx+D+WxKsIek++8zlSGnpJffh/iQgCUEZFDOM
	a8MJVZwwYYptnULaHKKEFMSm7qDYPsm7YqSwMLY00f6ZVbtUPeGfAdY8eL105agh
	zEnpKax4RKw3+Uk=
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-01-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: U2FsdGVkX19jlPd7N7qwj6/L2Guvtsj7
Date: Thu, 15 May 2014 01:25:47 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Default manifest
Message-ID: <20140515052547.GA3788@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5374053E DOT 3080007 AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5374053E.3080007@cornell.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, May 14, 2014 at 08:07:26PM -0400, Ken Brown wrote:
>Are we close to a resolution of the problems with default manifests?  It 
>looks to me like all the pieces are in place, but maybe I've missed 
>something:
>
>   https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01387.html
>   https://sourceware.org/bugzilla/show_bug.cgi?id=16790#c9
>   https://sourceware.org/bugzilla/show_bug.cgi?id=16807#c8
>
>I'm not trying to rush any maintainers, but I'm asking because I 
>currently have to use a self-built version of binutils, which doesn't 
>provide a default manifest, because of the problem I reported here:
>
>   http://cygwin.com/ml/cygwin/2014-04/msg00199.html

I'll update binutils ASAP.

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