Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <00e001c117ea$560b93f0$0300a8c0@ufo> From: "Trevor Forbes" To: "cygwin-developers" References: <996329431 DOT 27668 DOT ezmlm AT sources DOT redhat DOT com> <3B63432E DOT 6050309 AT ece DOT gatech DOT edu> <002101c117de$506d8d60$0300a8c0 AT ufo> <20010728232901 DOT A1707 AT redhat DOT com> Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin Date: Sun, 29 Jul 2001 14:22:56 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 ----- Original Message ----- From: "Christopher Faylor" To: "Trevor Forbes" 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