On 02/13/2012 02:42 PM Dale Hubler wrote:
Hello,
I was requested to install pypy but our computers appear to be too new
to run it, having libssl.so.0.9.8e among other newer items. This
confuses me because the web page for pypy shows a 2011 date and blog
entries from 2012. Can 2005 SSL really be a requirement, I am unable
to install such an old item on a cluster where this software might be used.
I looked at the pypy site but cannot find any supported platforms,
install guide, etc. I am trying this on RedHat EL 5. I tried the
binary release, but it also had the same error, no libssl.so.0.9.8,
which is true, my systems are updated. I must be missing something.
Do you have any links or other on-line info explaining how to build pypy.
thanks,
Dale
FWIW, I've been wondering what this difference means re SSL:
__________________________________________
[18:57 ~/wk/llac/bin]$ grep -i openssl <(strings $(which pypy))
OpenSSL_add_all_digests
OPENSSL_0.9.8
OPENSSL_VERSION
openssl_sha224
openssl_sha512
openssl_sha384
openssl_sha1]
OPENSSL_VERSION_INFO]
OPENSSL_VERSION_NUMBER
openssl_sha256
openssl_md5
OpenSSL 0.9.8k 25 Mar 2009
Returns 1 if the OpenSSL PRNG has been seeded with enough data and 0 if
not.
Mix string into the OpenSSL PRNG state. entropy (a float) is a lower
[18:58 ~/wk/llac/bin]$ grep -i openssl <(strings $(which python))
[18:58 ~/wk/llac/bin]$
__________________________________________
(i.e., openssl doesn't appear in python, but does in pypy. Linked differently?)
Regards,
Bengt Richter
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
