Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <38D25CB6.63BA065D@attglobal.net>
Date: Fri, 17 Mar 2000 11:26:30 -0500
From: John Fortin <fortinj AT attglobal DOT net>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: File permision errors on win98 with net release candidate
References: <20000317155549 DOT 19900 DOT qmail AT web122 DOT yahoomail DOT com> <20000317110225 DOT A15494 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Faylor wrote:

> On Fri, Mar 17, 2000 at 07:55:49AM -0800, Earnie Boyd wrote:
> >--- John Fortin <fortinj AT attglobal DOT net> wrote:
> >> Earnie Boyd wrote:
> >>
> >> > Hi John,
> >> >
> >> > Your problem might be due to autoconf itself.  I've been working with
> >> modifying
> >> > autoconf to work with Amol's ntport of zsh and had to modify it to look for
> >> > m4.exe, gawk.exe, etc instead of just m4, gawk, etc.  The function is
> >> > AC_PATH_PROG in acgeneral.m4.  You'll have to modify the configure by hand
> >> to
> >> > bootstrap.  See line 545 of configure for the check for gm4, gnum4 and m4.
> >> >
> >> > Earnie.
> >> >
> >>
> >> Hi Earnie,
> >>     But this worked in the past without any problems.  And other packages are
> >> broken too ( grep, fileutils for instance).
> >
> >Uhm, what shell are you using?  It appears that `test -f' isn't working
> >correctly for you.
>
> Can someone take a look at the configure code that is failing, pare it down
> to a simple test case and either report it here or, even better, run strace
> on a failing shell and send it here?

I'll try it tonight...

John