You've presented a very useful summary of your build.
For what it is worth, with the [EMAIL PROTECTED] kit
I obtained these test results on VMS 7.3-1 using
Compaq C V6.5-001:
lib/File/Find/t/find.................FAILED at test 1
lib/File/Find/t/taint................FAILED at test 1
lib/Net/Ping/t/190_alarm.............FAILED at test 6
lib/Net/Ping/t/450_service...........FAILED at test 8
Failed 4 test scripts out of 681, 99.41% okay.
In my case the File::Find module routines like find()
or finddepth() do not seem to like recursing through
a directory when their start directories are specified
as either the unix or vms style File::Spec->curdir()
defaults of '.' or '[]' respectively.
In fact I can demonstrate the bug in File::Find with
a few one liners:
DCL can find the file:
$ set def disk$user:[perl]
$ dir [...]commonsense.t
Directory DISK$USER:[PERL.T.LIB]
COMMONSENSE.T;1 2 17-MAR-2003 09:39:28.27
But these one liners each using a separate synonym for the current
default directory do not work:
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'.')"
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'[]')"
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'sys$disk:[]')"
Nor if I even give full path names to the default directory:
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'disk$user:[perl]')"
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'/disk$user/perl/')"
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'/$1$dka200/perl/')"
If, on the other hand I give a starting point other than the default
directory,
e.g.:
$ perl "-Ilib" "-MFile::Find" -e "find({wanted=>sub{print if $_ eq
'commonsense.t'}},'t')"
commonsense.t
it is found quickly. It could be due to the $ dollar signs in the physical
and device names,
but if I use another logical name to point to the same location I still
can't get File::Find::find()
to recurse.
I note that you and I have failures with lib/Net/Ping/t/190_alarm.t test #
6, and
lib/Net/Ping/t/450_service.t test # 8. I think in my case it is due to
inability to
set non blocking mode of the opened socket. I wonder if the test should be
skipped if we have this config.sh variable set (or if we should have
configure.com
test for the non block-ability using fcntl that is required)?
$ sea config.sh d_fcntl_can_lock
d_fcntl_can_lock='undef'
Peter Prymmer
