This is the mail archive of the
mailing list for the Cygwin project.
Re: Bug somewhere between cygwin, gcc and cvs
On Wed, Dec 25, 2002 at 03:06:33PM -0500, Igor Pechtchanski wrote:
>On Wed, 25 Dec 2002, Christopher Faylor wrote:
>> On Wed, Dec 25, 2002 at 02:29:17PM -0500, Arkadiy Belousov wrote:
>> >The version currently available does not support specifying port in
>> >CVSROOT. And I need that for ssh tunneling.
>> >I do realize I am on the bleeding edge here. Still, it's something to
>> >look at when CVS 1.11.2 is ported. Personally, I think it's the
>> >compiler. Let's wait till gcc loses (prerelease) label on it.
>> Despite appearances to the contrary, cygwin's gcc is based on the
>> released version of gcc 3.2. There is no better version being planned.
>> It sounds to me like this is a problem with opening a directory using
>> open, as was previously suggested.
>If I understand the documentation at
>corectly, open()ing a directory is not explicitly prohibited (in fact, the
>phrasing of one error value,
> The named file is a directory and oflag includes O_WRONLY or O_RDWR.
>suggests that it is allowed). Besides, the code only uses the file
>descriptor in a subsequent call to fchdir()... Am I missing something
You may be missing the fact that saying "a problem with opening a directory"
is not equivalent to saying "Cygwin isn't supposed to work this way."
Pierre Humblet submitted a patch to fix a problem opening directories on
Windows 9x/Me last week.
So, as always, trying a new cygwin snapshot is a good idea.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html