Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 1 Nov 2000 08:38:29 -0500
From: Andy Philpotts <andy DOT philpotts AT calendarcentral DOT com>
X-Mailer: The Bat! (v1.47 Halloween Edition)
Reply-To: "andy.philpotts" <andy DOT philpotts AT calendarcentral DOT com>
Organization: Product Development
X-Priority: 3 (Normal)
Message-ID: <73513460386.20001101083829@calendarcentral.com>
To: Christopher Faylor <cygwin AT sources DOT redhat DOT com>
Subject: Re[2]: latest cygwin does not track pwd?
In-reply-To: <20001101005246.A6570@redhat.com>
References: <14847 DOT 5635 DOT 636000 DOT 348903 AT gargle DOT gargle DOT HOWL>
 <4 DOT 3 DOT 1 DOT 2 DOT 20001031140921 DOT 02027560 AT pop DOT ma DOT ultranet DOT com>
 <20001031142519 DOT B28272 AT redhat DOT com> <39FF9C8C DOT 7597BC80 AT ece DOT gatech DOT edu>
 <20001101005246 DOT A6570 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Christopher,

I agree with you wrt it being undesirable to accomodate a perl bug.

Are you also setting errno to EINVAL? I'd refer to the source for
cygwin but I'm too busy downloading the source to perl!

Wednesday, November 01, 2000, 12:52:46 AM, you wrote:

CF> On Tue, Oct 31, 2000 at 11:31:08PM -0500, Charles Wilson wrote:
>>Christopher Faylor wrote:
>>cwd =
>>
>>just as Richard Kim says.  The code for Cwd::cwd on cygwin is
>>implemented by <perl-src>/cygwin.c -- but I don't know why it's
>>failing.  Patches gratefully accepted (and archived -- I'm not planning
>>to release a new perl build myself until 5.6.1 comes out; and probably
>>not even then if a third party takes the initiative...

CF> The problem is that it looks like perl is calling getcwd like this:

CF> getcwd (NULL, 0);

CF> and cygwin is returning a NULL, as is mandated by both the Single Unix
CF> Specification and the linux man page.  1.1.4 allowed zero length length
CF> arguments but that was a bug that I fixed in 1.1.5.

CF> I had no idea that people were relying on the bug.

CF> I'm not sure what to do about this.  I am loathe to accomodate a bug
CF> like this but I don't want to force a new perl release or endure to the
CF> next two years of "I cygwined my perl 1.1.[5-9] and it am broke" messages
CF> either.

CF> cgf

CF> --
CF> Want to unsubscribe from this list?
CF> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com



--
Andy Philpotts
Senior Software Developer
CalendarCentral Inc.
[w] 919/654-6200  xt.155
[c] 919/656-1166
[e] andy DOT philpotts AT calendarcentral DOT com
[www] www.calendarcentral.com

Andy says: I just got lost in thought. It was unfamiliar territory 



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com