Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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 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> <4015B3ED DOT 1060604 AT acm DOT org> In-Reply-To: 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/