This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin
- To: "cygwin-developers" <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin
- From: "Trevor Forbes" <trevorforbes at ozemail dot com dot au>
- Date: Sun, 29 Jul 2001 14:22:56 +0930
- References: <996329431.27668.ezmlm@sources.redhat.com> <3B63432E.6050309@ece.gatech.edu> <002101c117de$506d8d60$0300a8c0@ufo> <20010728232901.A1707@redhat.com>
----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: "Trevor Forbes" <trevorforbes@ozemail.com.au>
Sent: Sunday, July 29, 2001 12:59 PM
Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin
> On Sun, Jul 29, 2001 at 12:56:52PM +0930, Trevor Forbes wrote:
> >> On the down side, I do have this mktemp installed on my development
> >> machine, but I still saw the errors when running the autoconf test
suite
> >> under cygwin-CVS. However, I didn't know at the time to check that the
> >> test suite was actually using it.
> >>
> >> --Chuck
> >>
> >Chuck, I tested your version and well ......it did not perform nowhere
near
> >as good....and yes it produced errors with file collisions..
> >
> >Try the other version, and see what you think..
>
> Is anyone investigating the possibility that this is an ash bug?
>
> Do we have an understanding of what the actual problem is here?
>
> cgf
Hmmm......
Chris, following your lead, I turned Vfork off and rebuilt ash. I am
presently testing but so far there is no files in the temp dir and all the
autoconf tests are passing.
Trevor