Quantcast
Channel: ActiveState Community Site - PPM
Viewing all articles
Browse latest Browse all 154

Bad Install of Win32::API on Activestate Test Servers?

$
0
0

Our module is passing tests on all of the 32-bit ActiveState test servers, and passing on the 64-bit Perl V5.12 test server, but it's failing on both Perl V5.14 and V5.16 64-bit.

The root cause appears to be an XS/Perl mismatch for Win32::API. Here's the relevant snippets from your build logs:

From your build of our module on 64 bit Perl V5.14:

Win32::API object version 0.62 does not match $Win32::API::VERSION 0.63 at C:/Perl64-5.14/lib/DynaLoader.pm line 214.

And, from your build of our module on 64 bit Perl V5.16:

Win32::API object version 0.73 does not match $Win32::API::VERSION 0.75 at C:/Perl64-5.16/lib/DynaLoader.pm line 214.

We're not explictly calling out Win32::API as a prerequisite. We do mark Win32::SerialPort as a prereq, which is what is pulling in Win32::API. Other than that, we're not doing anything in our Build.PL or Makefile.PL (that I can see) that would trigger this sort of problem.

On the other hand, I see other modules that use Win32::API building just fine. Not sure if it's just a "luck of the draw" thing where their tests land on a different server, or if we're doing something wrong in our packaging, build scripts, etc.

Does this look to be an issue with the test servers, or something we're doing wrong?


Viewing all articles
Browse latest Browse all 154

Trending Articles