At 11:35 PM +0000 2/2/08, Nicholas Clark wrote: > >I'm curious how it fares on VMS, and which changes I've not integrated that I >should do to fix problems on VMS,
As of 33210 (I can't do builds as fast as you can integrate), with HP C V7.3-009 on OpenVMS Alpha V8.3 I get: t/io/fs.....................................FAILED at test 5 t/lib/vms_stdio.............................FAILED at test 2 lib/ExtUtils/t/cd...........................FAILED at test 1 lib/ExtUtils/t/eu_command...................FAILED at test 21 lib/ExtUtils/t/xs...........................FAILED--non-zero wait status: 1024 lib/Test/Harness/t/failure..................FAILED--expected test 3, saw test 2 Failed 6 tests out of 1036, 99.42% okay. vms_stdio.t needs 32791 integrated (which I just mailed you off-list about). lib/ExtUtils/t/xs fails like so: $ perl [-.lib.extutils.t]xs.t 1..0 # Skip ExtUtils::CBuilder not installed or couldn't find a compiler %SYSTEM-F-ABORT, abort If we aren't going to have CBuilder in 5.8.x, maybe xs.t should not even be in the distribution, though it's curious that C<plan skip_all> causes a failure exit condition. eu_command.t passes when run outside of the test suite. The others need more investigation, but I think I'll synch up with latest first. > John E. Malmberg made several VMS changes to File::Find, > which I think related to symlinks, but I'm not sure. They're not in. > Does it break things if they go in? Good question. I'll look them up and see what they are. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
