latest cygwin does not track pwd?
Andy Philpotts
andy.philpotts@calendarcentral.com
Wed Nov 1 05:38:00 GMT 2000
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@sourceware.cygnus.com
--
Andy Philpotts
Senior Software Developer
CalendarCentral Inc.
[w] 919/654-6200 xt.155
[c] 919/656-1166
[e] andy.philpotts@calendarcentral.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@sourceware.cygnus.com
More information about the Cygwin
mailing list