[SOLVED] Perl - undefined symbol error since -current updates

dsbx · 08-30-2017, 07:53 AM

Delete this post if possible.

dsbx · 08-30-2017, 08:30 AM

Yes, here is the error I get when using the Kx module.

Code:

perl: symbol lookup error: /<path>/<to>/perllib/lib64/perl5/auto/Kx/Kx.so: undefined symbol: Perl_Gthr_key_ptr

After a review this morning, all the systems that use this module with no issue are running Centos 6.5, including the server on which the module was built. The server that is having issues is running Centos 7.2, so perhaps that's why.

That said, I do think it's odd that a fresh Perl v5.10.1 instance on Centos6.5 is also getting the same error.

zakame · 08-30-2017, 10:18 AM

Seems to me you have Kx built from a perl with threads (note the undefined symbol) and loading them on another perl without threads.

dsbx · 08-30-2017, 10:32 AM

Quote:

Originally Posted by zakame

Seems to me you have Kx built from a perl with threads (note the undefined symbol) and loading them on another perl without threads.

you are partially correct.

The new build of 5.10.1 that I did has no threads.

The build of 5.16.3 does have threads.

dsbx · 08-30-2017, 11:27 AM

Quote:

Originally Posted by zakame

Seems to me you have Kx built from a perl with threads (note the undefined symbol) and loading them on another perl without threads.

I rebuilt my new 5.10.1 with threads, and this solved that issue, so now both 5.10.1 instances can run the Kx module successfully.

But the issue where 5.16.3-threaded fails on loading Kx persists.

zakame · 09-04-2017, 09:24 PM

FWIW, since your core problem is to get your Kx-using script to run on all your supported Perls, maybe another approach is to build a portable version of your script using something like pp from PAR::Packer? There's also the recently announced stew dependency packager. I've done a similar thing before with Crypt::LE, so maybe this can help you too.

dsbx · 09-07-2017, 12:51 PM

Quote:

Originally Posted by zakame

FWIW, since your core problem is to get your Kx-using script to run on all your supported Perls, maybe another approach is to build a portable version of your script using something like pp from PAR::Packer? There's also the recently announced stew dependency packager. I've done a similar thing before with Crypt::LE, so maybe this can help you too.

was talking with a co-worker about compiling everything into an executable to avoid these types of issues, so yeah I'll look into stew. For now I've built perl on a shared volume accessible from all hosts in question, and we'll use that one going forward.