this palemoon/perl error make sense to anyone?

trollog · 02-25-2017, 06:26 PM

trying to build khronoschotty's palemoon 27.1.1 from Sbo

this isn't the only thing I have tried to build lately that
threw this back at me.

makeinfo -I. ./autoconf.texi --no-split --output=autoconf.info
Cwd.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)

Arch seems to be having a similar issue with it's perl, but reading those threads got me nowhere.

Ztcoracat · 02-25-2017, 10:06 PM

I read a few of the Arch Linux articles about it and like you, wasn't able to find a solution either.

It's a bug in Debian:
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=810326

Someone found a solution for his Debian system but I'm not sure if that will give you want you need for your Slack install.
https://github.com/perseo22/pacmanager/issues/15

https://docs.slackware.com/howtos:software

alemoon

What I'd like to know is what generated the binaries to become mismatched:-
http://www.perlmonks.org/?node_id=1163254

Palemoon is maintained by: pomfland.
Maybe write to him and he'll know what the deal is. (just an idea you don't have to)

http://www.linuxquestions.org/questi...te-4175589512/

Ztcoracat · 02-25-2017, 10:26 PM

I'm not sure but maybe this is what is going on?

Quote:

It compiles the module using one version of perl and then tries to run the tests using another version of perl.

http://www.perlmonks.org/?node_id=1135612

I checked on my system and I have perl 5.22 installed.
[ installed ] - perl-5.22.2-x86_64-1
[ installed ] - perlkde-4.14.3-x86_64-2
[ installed ] - perlqt-4.14.3-x86_64-2

I think your best bet is to follow the instructions here and see if that works.
https://docs.slackware.com/howtos:software

alemoon

I hope other members running Pale Moon chime in to help you.

Sorry I don't know more. I gave it my best.

trollog · 02-26-2017, 12:31 AM

I am using Khronoschotty's build not pomfland's.

Khrono's previous builds always built flawlessly on current 64.

ponce · 02-26-2017, 02:01 AM

I just tried building this on slackware64-current and everything went fine.

I suppose your issue is caused because you installed some third party perl modules or something from CPAN: see the bug report below

https://bugzilla.redhat.com/show_bug.cgi?id=1425015

trollog · 02-26-2017, 04:01 AM

rm -fr a lot of perl5 dirs down in /usr seems to have fixed it.

uninstalling/reinstalling perl via slackpkg didn't fix it. Had to do some rm -fr ing after
uninstalling perl package w/pkgtools

After manually rm -fr ing, straight reinstall of perl via slackpkg fixed it. Palemoon appears to
be compiling fine now 5 mins into the compile. Compile was bombing in seconds before this.

Perhaps an old module. Not a perl user myself. Mostly it sits idle on my system. I prefer python.

FTIO · 02-26-2017, 07:32 AM

Khronoschotty's build on my x64 system crashed 5 seconds after it started up (it seemed to build fine though).

I then uninstalled that build and downloaded the tarball straight from Palemoon's site to run from its own directory and *that* is running fine. Strange.

ponce · 02-26-2017, 08:00 AM

Quote:

Originally Posted by FTIO

Khronoschotty's build on my x64 system crashed 5 seconds after it started up (it seemed to build fine though).

have you checked this note from the README?

Code:

If your processor doesn't support sse2 instructions or you get segfaults,
try looking in the SlackBuild for the OPTIMIZE build option (eventually
refer to the Pale Moon developers for help).

Code:

# You can try changing the optimization level to simply "-O2" if your processor
# doesn't support sse2 instructions.
# "-Os" might help if you experience segfaults.
OPTIMIZE=${OPTIMIZE:-"-O2 -msse2 -mfpmath=sse"}

Ztcoracat · 02-26-2017, 04:04 PM

Quote:

Originally Posted by trollog

rm -fr a lot of perl5 dirs down in /usr seems to have fixed it.

uninstalling/reinstalling perl via slackpkg didn't fix it. Had to do some rm -fr ing after
uninstalling perl package w/pkgtools

After manually rm -fr ing, straight reinstall of perl via slackpkg fixed it. Palemoon appears to
be compiling fine now 5 mins into the compile. Compile was bombing in seconds before this.

Perhaps an old module. Not a perl user myself. Mostly it sits idle on my system. I prefer python.

Glad to hear removing perl5 fixed it.

What are the differences between Khronoschotty's build and pomfland's build?

orbea · 02-26-2017, 06:34 PM

khronosschoty's build compiles palemoon from source, pornfland's repackages the official palemoon binary.

Ztcoracat · 02-26-2017, 07:07 PM

Quote:

Originally Posted by orbea

khronoschotty's build compiles palemoon from source, pornfland's repackages the official palemoon binary.

Knowing the difference is important:- Thanks

Are you in favor of one over the other?

I prefer src:-

orbea · 02-26-2017, 08:11 PM

I prefer compiling it myself as well, but with all due honestly I have not been able to comfortably move from firefox to palemoon yet. That is just me though.

FTIO · 02-26-2017, 08:46 PM

Quote:

Originally Posted by ponce

have you checked this note from the README?

Code:

If your processor doesn't support sse2 instructions or you get segfaults,
try looking in the SlackBuild for the OPTIMIZE build option (eventually
refer to the Pale Moon developers for help).

Code:

# You can try changing the optimization level to simply "-O2" if your processor
# doesn't support sse2 instructions.
# "-Os" might help if you experience segfaults.
OPTIMIZE=${OPTIMIZE:-"-O2 -msse2 -mfpmath=sse"}

Yep, sure did, before I compiled it. Checked just for the heck of it and my cpu supports sse2 (AMD FX-8350). I won't sweat it since it works with the blob. Nice thing about the compiled one though before it simply disappeared off the screen was that it started up almost instantaneously...literally a second or less after I clicked on the icon in the menu. The blob starts up fast but not quite as.

trollog · 02-27-2017, 04:45 PM

I switched over to palemoon when Khronosschotty released his first build.

This compile issue is the first trouble I have had with it- and it's a perl issue
not a PM issue.

Otherwise PM has always compiled without trouble, provided you use all the
files that come with the Slackbuild.

Gnu Taler doesn't work quite right with anything but FF but truth be told Taler is
an obscure piece of software at best right now.

Otherwise not a single problem with PM on windows7 or Slackware.

What small utube and flash peculiarities and misbehaviors I have observed also occur
under FF.

All in all PM has been pretty solid. Even works fine with things like university
online class websites which are a mess.

Even those that can't identify the browser.

PM development seems very MS and Win-centric, but that can change over time. The fundamentals
are present and seem solid at this point.
.

Ztcoracat · 02-28-2017, 01:31 AM

Quote:

Originally Posted by orbea

I prefer compiling it myself as well, but with all due honestly I have not been able to comfortably move from firefox to palemoon yet. That is just me though.

Thanks for the details.