[Mailman-Users] ImportError: ld.so.1: /usr/local/bin/python: fatal: libssl.so.0.9.6: open failed: No such file or directory
jwarnier at mrbc.irisnet.be
Tue Dec 4 10:06:17 CET 2001
> On 03 December 2001, Jerome Warnier said:
> > The subject is the error I get every single time a script has to be
> > executed from Mailman.
> Your Python installation is broken.
I understood that, but how do I fix it? I cannot get to recompile Python!
> > On the other side, I don't understand why it needs so much OpenSSL, as
> > I'm not willing to use it (I'm willing to run Mailman on a private
> > network).
> It doesn't need OpenSSL, but recent versions of Python will use OpenSSL
> if they find it *at build-time*. If things change --
> eg. libssl.so.0.9.6 was on the system where you built Python, but not on
> the system where you're running it -- then Python will be unable to load
> the socket module, which Mailman is heavily dependent on.
The problem is that they are both installed and even when I create symlinks, it
doesn't work. It goes further(the libraries needed are found, except one) but
keeps saying the same thing for "libcrypt.so.0". I'm stuck.
> > I'm in trouble because I cannot get to recompile nor Python2.1.1 nor
> > OpenSSL on my Sun Entreprise 10000 running Solaris 8. It seems "as",
> > packaged with Solaris, doesn't understand some instructions.
> Sun has a long and glorious history of shipping broken software. (Come
> to think of it, so does every other computer manufacturer and software
> company on the planet.) Try gcc -- I've never had a problem building
> Python with gcc on Solaris.
Python and OpenSSL are not shipped with Solaris, I took the packages from
> Greg Ward - software developer gward at mems-exchange.org
> MEMS Exchange http://www.mems-exchange.org
More information about the Mailman-Users