Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Thu, 13 Feb 2003 10:13:22 -0500 From: Christopher Faylor 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] Message-ID: <20030213151322.GH27226@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030213144024 DOT GC27226 AT redhat DOT com> <3E4BB4EE DOT 6DF1C18B AT ieee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E4BB4EE.6DF1C18B@ieee.org> User-Agent: Mutt/1.5.1i On Thu, Feb 13, 2003 at 10:08:30AM -0500, Pierre A. Humblet wrote: > > >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. It's not bash, it's ash. cgf