Class::BuildMethods is still not available from ActiveState on several platforms. Here's all of the build information I have (for Windows):
D:\cpanrun\build\5-8-0\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t
t/00-load....# Tesok
t/10-basic........dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-50
Failed 50/50 tests, 0.00% okay
t/20-classdata....dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-11
Failed 11/11 tests, 0.00% okay
t/pod-coverage....skipped
all skipped: Test::Pod::Coverage 1.04 required for testing POD coverage
t/pod.............skipped
all skipped: TestFailed 2/5 test scripts, 60.00% okay.Failed Test Stat Wstat Total FaiNMAKE : fatal error U1077: 'D:\cpanrun\build\5-8-0\bin\perl.exe' : return code '0xff'
Stop.
------------
t/10-basic.t 255 65280 50 50 100.00% 1-50
t/20-classdata.t 255 65280 11 11 100.00% 1-11
2 tests skipped.
Once again, I have no way of using that information to figure out what's wrong. Using the exact same build command on my Mac passes. I no longer have any external dependencies except Test::More (any version), so even their &Scalar::Util::refaddr problem isn't involved any more. I'll drop them another email, but this is frustrating.
Update: I've found the problem, but I'm going to see if I can convince ActiveState to report verbose test information. That's a simple matter of changing this:
test_harness(0, 'blib\lib', 'blib\arch')
To this:
test_harness(1, 'blib\lib', 'blib\arch')
Of course, given how many modules they're testing, this may prove problematic, but it would be a great help to module authors.