On Jul 28, Dominic Dunlop said: >The following (coarsely wrapped) is the proximate cause of a test >failure in lib/findbin.t for perl-current@6450: > >$ ./perl -I../lib -MCwd=getcwd -lwe 'print getcwd' >lstat(OUCH...) >This, in turn is a result of the changes made to Cwd.pm by change 6429. >I have not analysed what's going on, but I'd bet that it's something to >do with MachTen, which is 4.4BSD UNIX hosted by Mac OS, being a "root >in the sky" implementation: the UNIX file hierarchy sits under / (as >one expects), but, (as one wouldn't expect), // is the Mac OS volume >under which MachTen's files live. To round things off, /.. is >equivalent to / (as one would expect). This is OK by POSIX, which says >"[a] pathname that begins with two successive slashes may be interpreted >in an implementation-defined manner, although more than two leading >slashes shall be treated as a single slash." That would be my bad touch. >My (not disinterested) feeling is that Perl should work with systems >whose idiosyncrasies are permitted by POSIX. Does this analysis make >sufficient sense for you to be able to propose a fix, or would you >prefer me to have a hack at the problem? You sound more learned with the MachTen... would you mind taking a hack at it? -- Jeff "japhy" Pinyan japhy@pobox.com http://www.pobox.com/~japhy/ PerlMonth - An Online Perl Magazine http://www.perlmonth.com/ The Perl Archive - Articles, Forums, etc. http://www.perlarchive.com/ CPAN - #1 Perl Resource (my id: PINYAN) http://search.cpan.org/Thread Next