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=e/hSzjSL8sS2f3KXv56SpXDlyv41Nt3PZDJOqfvKWTgFmh6izB4US
	SgeHR/u/jKSco6jCM/uo73JQ4kF08xph7arC1PsPl9kFmXanYwPx6ltrURV8dOKj
	wwTJgNS2J1PMwyIcfLVoSoEPYrklATE2pAe++TK9pFzRWpPtK0t748=
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=LsONu85BkE8AJuAMcYjr2Osh5BQ=; b=UhC/bKB9V2UECk/uilHWgYS9g+pR
	S/NID4p+uZ1hqmqFXsPlVJEMMK54g0R6Btsf4RoR8EpNO0WWw3kL3AOP+ZFt12+I
	plsSsIzjGBQjZnVKLAF6ciQj67xDzCw6fKyV04TtNai/xFPawqpfQosGGmbckm38
	Q2fUYnUi1+OrK+c=
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-Spam-SWARE-Status:	No, score=2.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:	U2FsdGVkX19OYn2NL6mgvoCHscRZt3Xi
Date:	Sat, 5 Oct 2013 01:13:04 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: w32api-headers-3.0.0.-1 in question
Message-ID:	<20131005051304.GB8173@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<248766acf83f2eac3d93e900b99761a7 AT denis-excoffier DOT org> <524F6C9E DOT 8080404 AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<524F6C9E.8080404@gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Sat, Oct 05, 2013 at 09:34:22AM +0800, JonY wrote:
>On 10/4/2013 18:02, Denis Excoffier wrote:
>> Hello,
>> 
>> I use cygwin 32 bits, last snapshot.
>> 
>> Since the last update of
>> - mingw64-i686-headers-3.0.0-1
>> - mingw64-i686-runtime-3.0.0-1
>> - w32api-headers-3.0.0-1
>> - w32api-runtime-3.0.0-1
>> (see http://cygwin.com/ml/cygwin-announce/2013-09/msg00018.html)
>> 
>> i'm no longer able to compile the last cygwin snapshot (20130925).
>> With the Previous issues of these packages (3.0b_svn5935), all is ok.
>> 
>
>Corinna, cgf, last time, Kai mentioned that these were added recently,
>Cygwin might have been declaring it on its own.

You know, in other projects people actually track down problems and
provide patches without just offering surmises or bug reports.  It's sad
that Cygwin as so few people who are willing to fix problems, especially
when they are as simple to track down as this.

--
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

- Raw text -