X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Thu, 27 Jan 2011 10:06:21 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Still on target for imminent 1.7.8 release? [was Re: Enable dfp routines in compiler support lib]
Message-ID:	<20110127090621.GA9134@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4D3EF76F DOT 7090408 AT users DOT sourceforge DOT net> <4D3F7C6F DOT 4060600 AT gmail DOT com> <4D3F76E2 DOT 80207 AT users DOT sourceforge DOT net> <4D3F9AC6 DOT 3040605 AT gmail DOT com> <20110126103331 DOT GK28470 AT calimero DOT vinschen DOT de> <1296083106 DOT 2856 DOT 3 DOT camel AT YAAKOV04>
MIME-Version:	1.0
In-Reply-To:	<1296083106.2856.3.camel@YAAKOV04>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Jan 26 17:05, Yaakov (Cygwin/X) wrote:
> On Wed, 2011-01-26 at 11:33 +0100, Corinna Vinschen wrote:
> > On Jan 26 03:53, Dave Korn wrote:
> > >   Hey, main list!  Are we still expecting 1.7.8 by the end of this month?
> > 
> > Early Feb is more likely.  From my POV there's just that new issue with
> > stdio blocking each other.  Chris, are you still working on something
> > for 1.7.8?
> 
> How about this issue since 1.7.7:
> 
> http://cygwin.com/ml/cygwin/2010-12/msg00450.html

I, for one, have not seen this error.  Maybe I'm not building as
large projects as you do, but either way, it would be helpful if
you would try to track it down.

For instance, do you have a stacktrace, using the latest snapshot, or
better, Cygwin from CVS?  Did you try to back out the changes from the
20100901 snapshot to see which one of them is the culprit?  From the
ChangeLog I don't see anything obvious.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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