Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<401689E3.3090806@acm.org>
Date:	Tue, 27 Jan 2004 07:55:15 -0800
From:	David Rothenberger <daveroth AT acm DOT org>
Reply-To:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version:	1.0
To:	Brian Ford <ford AT vss DOT fsi DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re: ash signal problems with latest CVS
References:	<16405 DOT 41671 DOT 479106 DOT 886434 AT forbin DOT entomo DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0401261820070 DOT 11773 AT eos> <4015B3ED DOT 1060604 AT acm DOT org> <Pine DOT GSO DOT 4 DOT 58 DOT 0401270944390 DOT 11773 AT eos>
In-Reply-To:	<Pine.GSO.4.58.0401270944390.11773@eos>
X-IsSubscribed:	yes

Brian Ford wrote:

> Incidentally, is there a way to reliably compare two CVS built DLLs from
> the cygcheck or uname -a output?

I don't think so, since both just include the date the DLL was built.

> FWIW, this problem appears to be fixed by:
> 
> http://www.cygwin.com/ml/cygwin/2004-01/msg01160.html

Concur.

Dave




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -