At 12:11 PM +0100 11/7/04, Abe Timmerman wrote:

>I see this on Alpha (not on VAX!). It makes Test::Smoke on alpha rather hard.

I can't reproduce this, so the particular point of breakage may be
specific to the machine you are running on.

>TIMMERMAN:FASOLT$ type fftest.pl
>#! perl
>use warnings FATAL => 'all';
>use strict;
>
>use File::Find;
>use Cwd;
>
>my $ddir = 'disk$user_2:[timmerman.fasolt.perl-58x]';
>my $cwd = cwd();
>chdir $ddir or die "Cannot chdir($ddir): $!";
>File::Find::find( sub {
>    -d and print "$File::Find::name\n";
>}, '.' );
>chdir $cwd or die "Cannot chdir($cwd) back: $!";
>TIMMERMAN:FASOLT$ perl fftest.pl
>.
>./x2p
>./wince
>./wince/include
>./wince/include/sys
>./wince/include/arpa
>./wince/bin
>Can't cd to (./) win32: invalid argument
> at fftest.pl line 13
>%SYSTEM-F-ABORT, abort
>
>Does anyone know why, or a way around it?

What version of Perl and/or File::Find?  File::Find has had at least
a couple pretty serious bugs fixed sometime in the Perl 5.8
timeframe.  What you are seeing typically happens when there is a
logical name that coincides with a subdirectory name.  I believe this
has been fixed in current versions of File::Find, but if you've got
Perl 5.6.1 you will probably still see it.

I'm not 100% sure this is the problem you are encountering, but you
can check for the existence of logical names that might be throwing
it off track:

$ show logical include
$ show logical win32

Another odd thing in the output you posted is the order of the
directories it finds.  When I run your script with maintperl, the end
of the list looks like:

./vms/ext/stdio
./vos
./win32
./win32/bin
./win32/ext
./win32/ext/win32
./win32/include/arpa
./win32/include/sys
./wince
./wince/bin
./wince/include/arpa
./wince/include/sys
./x2p


so it's giving them to me in alphabetical order, but in your example,
it seems to think wince comes before win32.
-- 
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Reply via email to