Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3E4BB4EE.6DF1C18B@ieee.org>
Date: Thu, 13 Feb 2003 10:08:30 -0500
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: uh oh [Roland DOT Schwingel AT onevision DOT de: Re: bash broken with cygwin 
 1.3.20? - now working with 1.3.20]
References: <20030213144024 DOT GC27226 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Christopher Faylor wrote:
> 
> Ok, what's causing these type of problems in 1.3.20?  There has been a
> few of these reported.
> 

> > Please post the output of 'ls -l ../gcc-3.2.1/configure.in'.
> -rwx------+   1 Administ Entwickl    55070 Jul  8  2002
> ../gcc-3.2.1-ov/configure.in

Not sure how bash looks up the access mode.
I have some evidence that access() is broken but can't debug until tonight.

Pierre