This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: uh oh [Roland.Schwingel@onevision.de: Re: bash broken with cygwin 1.3.20? - now working with 1.3.20]
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 13 Feb 2003 10:13:22 -0500
- Subject: Re: uh oh [Roland.Schwingel@onevision.de: Re: bash broken with cygwin 1.3.20? - now working with 1.3.20]
- References: <20030213144024.GC27226@redhat.com> <3E4BB4EE.6DF1C18B@ieee.org>
- Reply-to: cygwin-developers at cygwin dot com
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