Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4E06A937DADC3842ACE4D3A1096A9EAC038C6D@JANUS.eecs.berkeley.edu> From: George Necula To: "'Gerrit P. Haase'" , cygwin AT cygwin DOT com, perl5-porters AT perl DOT org Subject: RE: Sorry... (was: Re: Bug: cygwin Perl uses File/Spec/Unix.pm in stead of File/Spec/Win3 2.pm) Date: Tue, 2 Apr 2002 08:28:49 -0800 MIME-Version: 1.0 Content-Type: text/plain I have fixed the bug in my copy by changing the implementation of File::Spec::Unix->file_name_is_absolute to check whether $^O is cygwin and use the rule from Win32.pm. There are other places in the file where such conditionals occur. As to one of the previous replies saying to use ActivePerl on Windows, that is not helpful at all. ActivePerl won't understand /cygdrive/c notation, which makes it hard to have a cygwin installation working with ActivePerl. So far I noticed that the C:/Test notation is understood by everybody (cygwin, Windows tools) so it seems like a good middle ground. George. > -----Original Message----- > From: Gerrit P. Haase [mailto:freeweb AT nyckelpiga DOT de] > Sent: Tuesday, April 02, 2002 4:26 AM > To: George Necula; cygwin AT cygwin DOT com; perl5-porters AT perl DOT org > Subject: Sorry... (was: Re: Bug: cygwin Perl uses > File/Spec/Unix.pm instead of File/Spec/Win3 2.pm) > > > Gerrit schrieb: > > Not that nice, excuse me please. > > >> To reproduce the bug: > >> perl -e 'use File::Spec; print > >> File::Spec->file_name_is_absolute("C:/test") > >> ? "no bug" : "bug";' > > This should be handled by cygwin1.dll. > E.g. it is possible to type: > $ mkdir c:/test > $ ls c:/test > and so on. > Since CygwinPerl is linked against cygwin1.dll it should work > inside Perl too. > > > Gerrit > -- > =^..^= > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/