Re: Can I re-use modules compiled with a different build of Perl, but with the same version number on the same machine?

From doing research on the Internet, people have said that I would need to recompile the modules using the new build of Perl

That should fix the problem - but it shouldn't be necessary if the 2 perls in question match.
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 ... but maybe there's some other consideration.
For the 2 perls what is the output of

perl -le 'print $];'
[download]

and

perl -V:archname
[download]

If the outputs for the 2 perls are identical, then it's probably best to give us (in readmore tags) the entire perl -V output for both perls.
Someone might then be able to spot the snag.

Cheers,
Rob

Comment on Re: Can I re-use modules compiled with a different build of Perl, but with the same version number on the same machine? Select or Download Code

Replies are listed 'Best First'.
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 (Novice) on Feb 11, 2015 at 20:18 UTC
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.	[reply]

Replies are listed 'Best First'.

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 (Novice) on Feb 11, 2015 at 20:18 UTC

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.

[reply]