Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Tue, 14 Sep 2004 10:04:15 -0400
From:	"Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)
Message-ID:	<20040914140415.GA651435@Worldnet>
References:	<00f401c497cd$a803aec0$0b03a8c0 AT lithium> <015101c49932$e1651850$0b03a8c0 AT lithium>
Mime-Version:	1.0
In-Reply-To:	<015101c49932$e1651850$0b03a8c0@lithium>
User-Agent:	Mutt/1.4.1i

On Sun, Sep 12, 2004 at 09:42:07PM -0400, Bogdan Vacaliuc wrote:
> 
> Anyway, the attached script (test-configure) will create the above configure.ac, generate configure (via. autoconf), and run the
> above line over and over until failure.  I am also attaching cygcheck.out for my environment as it now exists.

FYI, I lauched that script last evening, it's now at iteration 6441.
That's on NT4 with a 2 day old cygwin dll built from cvs.

I have seen all the latest e-mails in this thread and the plea 
to use the new snapshot.

BTW, checking for reused PIDs is a trace is very easy:
fgrep Program <the_trace>

Pierre

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