At 12:27 AM -0500 3/3/2000, Dan Sugalski wrote:
>At 11:53 PM 3/2/00 -0500, Charles Bailey wrote:
>>I managed to fold in (I think) all of the new VMS-specific changes
>>through early this evening (including a fix for the dratted ACCVIO --
>>an incorrect initialization of PERL_INC_VERSION_LIST in
>>subconfigure.com), re-integratied the mainline changes, and put
>>up a new test kit here (named, imaginatively, vmsperl_pre56_3.tgz).
>>Please grab and test as much as possible to pick up any last-
>>minute bugs.
>
>Alas, configure.com fails with:
>
>%DCL-W-UNDSYM, undefined symbol - check validity and spelling
> \USE_64BITINT\
>%DCL-W-UNDSYM, undefined symbol - check validity and spelling
> \PERL_I64SIZE\
>%DCL-W-UNDSYM, undefined symbol - check validity and spelling
> \PERL_U64SIZE\
>
>I think it's ok anyway. I've patched the fix (it's one of the ones I sent to Jarkko) 
>and am giving it a run now.

I saw the same thing, but got a successful build anyway after a -des
configure.  The test suite hung on openpid.t, as usual.  After
hacking that test to lie about its failure, I still get the following
failures further on in the test suite:


[.lib]filefind..........FAILED on test 18
[.lib]filespec..........FAILED on test 1
[.lib]vmsfspec..........FAILED on test 62
[.op]fh.................FAILED on test 5
[.op]taint..............FAILED on test 10
[.pragma]warnings.......FAILED on test 151

but at least it completed the suite, giving us a bottom line of

Failed 6/221 tests, 91.40% okay.  

This was with DEC C V5.2-003 on OpenVMS Alpha V7.1.

lib/filefind when run individually didn't say anything immediately informative (at 
least to me).

The lib/filespec test in detail looks like:

[.LIB]FILESPEC..........Prototype mismatch: sub File::Spec::VMS::unixify vs ($) at 
../lib/File/Spec/VMS.pm line 9
Prototype mismatch: sub File::Spec::VMS::vmspath vs ($) at ../lib/File/Spec/VMS.pm 
line 9
1..246
Can't make list assignment to %ENV on this system at [.lib]filespec.t line 340.
%SYSTEM-F-ABORT, abort


The lib/vmsfspec test is complaining about:

not ok 62  : vmsify('//some/where//over/../the.rainbow') expected 
|some:[where]the.rainbow|, got |some:[where.over.-]the.rainbow| 

The op/fh test fails with this followed by a register dump:

[.OP]FH.................1..5
ok 1
ok 2
ok 3
ok 4
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000000C, 
PC=00000000000A9938, PS=0000001B

and on that cheery note I'm going to take the rest of the evening off :-).

____________________________________________
Craig A. Berry                   
mailto:[EMAIL PROTECTED]

Reply via email to