At 9:14 PM -0400 4/4/04, John E. Malmberg wrote:
>I just have built Perl 5.8.3 on OpenVMS Alpha 7.3-2.
>
>When running the tests, the vmsish test failed.
>
>lib/vars.............................ok
>lib/vmsish...........................FAILED at test 25
>lib/warnings.........................ok

That was patched here:

http://public.activestate.com/cgi-bin/perlbrowse?patch=22223

>The same build on OpenVMS VAX 7.3 failed 8 tests.
>
>PYTHON> search build.log failed
>t/op/pack............................FAILED at test 0

Hmm.  That would be good to know about.  What do you get from

$ @[.vms]test .exe "" -"v" [.op]pack.t

?

>t/op/stat............................FAILED at test 75

This could be timezone setting related.

>lib/ExtUtils/t/basic.................FAILED at test 26
>lib/ExtUtils/t/Constant..............FAILED at test 23

Dunno about these.  There could be directory depth issues in the
tests themselves.

>lib/Math/BigInt/t/bare_mbi...........FAILED at test 2600
>lib/Math/BigInt/t/bigintpm...........FAILED at test 2600
>lib/Math/BigInt/t/sub_mbi............FAILED at test 2600

I think the BigInt module uses doubles to store chunks of very large
integers.  It probably makes some assumption that blows up on the
very limited exponent range of D_FLOAT, which is still the default
for Perl floating point on VAX.  You could do a G_FLOAT build or hack
into the innards of BigInt enough to see what it needs.  The author
has been very helpful sorting out similar situations in the past.

>lib/vmsish...........................FAILED at test 22

Any chance you haven't reset the clock since the daylight savings change?

>Failed 8 test scripts out of 760, 98.95% okay.

This has been better in recent memory.  I don't have any vaxen and
not many (any?) people who do are in the habit of building
development releases on a regular basis and reporting or fixing the
failures that show up.

-- 
________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]

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

Reply via email to