[SOLVED] -current perl ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xeb00080)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
-current perl ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xeb00080)
I'm trying to run a perl script in a new install of -current and getting the following error :
Code:
ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xeb00080)
My searching seems to indicate when a perl library is installed with a different version than what's installed such as installing via cpan or a package manager. But I've only installed Slackware-current and haven't installed any other perl packages.
if it's not that could it be also that the perl stuff you are trying to run has to be rebuild too against the newer perl in current (maybe because it contains additional perl modules itself).
So that's one of the places where I saw the notes about having modules installed separately, but I didn't install any, its a clean -current install.
so their suggestions such as checking
Its Slic3r. I was using it for the last few months on a raspberry pi 400 running Slackware-arm-current. If you download and extract you can then just run
Code:
perl slic3r.pl
. So I bought a small x86 desktop to upgrade from the Pi400 and installed -current and trying the same
Code:
perl slic3r.pl
gives the error. I hadn't updated the pi in a month or two is really the only difference i can find.
I followed the instructions on how to build it (because you have to build it, you cannot simply execute it as is moving the directory from one version to another of perl)
I installed perl-local-lib as requested and I issued these two commands
Code:
export LDLOADLIBS=-lstdc++
perl Build.PL
and here it asked me to install also cpanminus: I installed it too and then it started building a ton of other perl modules (they are still building)...
I have run those command as user to avoid an installation via cpanminus system-wide (I don't know where cpanminus install stuff).
EDIT: in the end the main slice3r.pl built fine (and run fine after), while the gui won't (with an error building Wx::build::MakeMaker) and, good news, cpanminus installed the stuff locally in a "local-lib" directory.
I went ahead and installed cpanminus via the Slackbuild and the Slic3r build as non-root and the Slic3r-build.pl still tells cpanminus to put stuff in a local-lib
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.