I would've expected that if both perls report the same version number, and the same archname then you shouldn't be experiencing this problem
It turns out, you were 100% correct. The local Perl built using the same version and specified archname (using the ./Configure flags mentioned above in my post) did fix the problem. The real issue it turns out was the test script that was pointing to a faulty build of Perl.
In reply to Re^2: Can I re-use modules compiled with a different build of Perl, but with the same version number on the same machine?
by neuty
in thread Can I re-use modules compiled with a different build of Perl, but with the same version number on the same machine?
by neuty
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |