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 X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Thu, 3 Apr 2003 09:25:04 -0600 (CST) From: Brian Ford X-X-Sender: ford AT eos To: Thomas Pfaff cc: cygwin Subject: Re: CVS winsup/testsuite/winsup.api/pthread/condvar9.c failure In-Reply-To: <3E8C0018.7030207@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 3 Apr 2003, Thomas Pfaff wrote: > I tried on XP and i was not able to reproduce. > Can you dig a little deeper ? > Sure. Two questions though. First, any pointers on where or how to start? I just thought you might have some specific questions that would lead us to the problem more quickly. Second, I wan't to make sure this isn't a false alarm as I am fairly new to building Cygwin. My sources are current as of this morning. Is this test proceedure valid? I simply made a build dir. Configured as "../cygwin/configure --prefix=/home/ford/cygtest". Ran "make; make check". How does the test framework handle cygwin1.dll conficts, if it does? ie. Do I need to stop all Cygwin processes before running make check? Do I need to install the new Cygwin before running make check? The FAQ appears to say no here. Last, how do you developers manage test running Cygwin versions and reverting. Obvioulsy, for things like the new 64 bit support, just swapping cygwin1.dll is not sufficient. Thanks. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/