Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <401689E3.3090806@acm.org>
Date: Tue, 27 Jan 2004 07:55:15 -0800
From: David Rothenberger <daveroth@acm.org>
Reply-To: cygwin@cygwin.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@vss.fsi.com>
CC: cygwin@cygwin.com
Subject: Re: ash signal problems with latest CVS
References: <16405.41671.479106.886434@forbin.entomo.com> <Pine.GSO.4.58.0401261820070.11773@eos> <4015B3ED.1060604@acm.org> <Pine.GSO.4.58.0401270944390.11773@eos>
In-Reply-To: <Pine.GSO.4.58.0401270944390.11773@eos>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/