Re: linker trying to load wrong file

You need to rebuild Crypt::SSLeay and install it again, since during the build process the SSLeay.so is built and linked against your libssl.so. If you remove that library, the file referenced by SSLeay.so cannot be found.

<update> But it seems to me that you are trying to solve a problem the wrong way... are you really sure the segfaults you pointed out in https request causes segmentation fault are being caused by the libssl.so? Downgrading often means "installing solved bugs". </update>

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: linker trying to load wrong file Select or Download Code

Replies are listed 'Best First'.
Re^2: linker trying to load wrong file by eisdrache (Novice) on Oct 30, 2006 at 10:26 UTC
well, yes, it does seem like a completely ass backwards approach to solving the problem, however, i was all out of options, so i was desperate to try anything. i removed the crypt::ssleay module and reinstalled it, but forwhatever reason it was still looking for the 0.9.8 file. i even reinstalled perl to no avail. so in another ass backwards move, i just created a link called libssl.so.0.9.8 and pointed it to libssl.so.0.9.7. on top of that, there must have been some kind of issue with openssl 0.9.8 becuase now everything works the way that it should.	[reply]
Re^3: linker trying to load wrong file by Intrepid (Curate) on Nov 01, 2006 at 10:03 UTC
eisdrache wrote on 30 Oct 2006 i removed the crypt::ssleay module and reinstalled it, but forwhatever reason it was still looking for the 0.9.8 file. I am very curious as to what the whatever reason reason was ;-). That sounds like a failure of a build support mechanism to work properly, and/or a failure of the operator building the module (yourself) to operate the build properly. In any case, the only thing I know of right now to advise you, is that in future cases like this, providing a link (at least) to the complete textual output of the build procedure steps (typically 'perl Makefile.PL <args...>' and then 'make'), would be valued by some of us (or maybe just me, in all the world, only me, sigh). ;-) Soren A / somian / perlspinr / Intrepid -- Words can be slippery, so consider who speaks as well as what is said; know as much as you can about the total context of the speaker's participation in a forum over time, before deciding that you fully comprehend the intention behind those words. If in doubt, ask for clarification before you 'flame'.	[reply]