question re: ancient SSL requirement of pypy
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 -- Dale Hubler dhubler@uw.edu (206) 685-4035 Senior Computer Specialist University of Washington Genome Sciences Dept.
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
Dale Hubler <dhubler@u.washington.edu> writes:
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.
I think it's just the pre-built binaries that have that dependency. ldd shows that the pypy I translated myself links against libssl.so.1.0.0. It is possible to translate pypy with cpython, though it takes something like twice as long as translating with a pre-built pypy. Instructions for translating here: http://doc.pypy.org/en/latest/getting-started-python.html
On Tue, Feb 14, 2012 at 12:42 AM, Dale Hubler <dhubler@u.washington.edu> 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
-- Dale Hubler dhubler@uw.edu (206) 685-4035 Senior Computer Specialist University of Washington Genome Sciences Dept.
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
It's not PyPy requirement, it's the binary requirement. To be honest, binary distribution on linux is a major mess. Fortunately for most popular distributions there is a better or worse source of official or semi-official way to get it directly from the distribution and that;'s a recommended way (fedora, ubuntu, debian, gentoo and arch package pypy).
On Tue, Feb 14, 2012 at 7:45 AM, Maciej Fijalkowski <fijall@gmail.com> wrote:
It's not PyPy requirement, it's the binary requirement. To be honest, binary distribution on linux is a major mess. Fortunately for most popular distributions there is a better or worse source of official or semi-official way to get it directly from the distribution and that;'s a recommended way (fedora, ubuntu, debian, gentoo and arch package pypy).
why not statically link everything and mark the pre built binaries a "security risk" or whatever and then they will just work. -- Leonardo Santagada
Hi Leonardo, On Fri, Feb 17, 2012 at 15:55, Leonardo Santagada <santagada@gmail.com> wrote:
why not statically link everything and mark the pre built binaries a "security risk" or whatever and then they will just work.
Anyone can either install PyPy from his own distribution, or translate it from sources; or attempt to get one of our nightly binary packages, which may or may not work because it's Linux. I think that this is what you get on Linux, and we will not try to find obscure workarounds (like making all our nightly binary packages twice as big just for this use case). A bientôt, Armin.
On Fri, Feb 17, 2012 at 3:23 PM, Armin Rigo <arigo@tunes.org> wrote:
Hi Leonardo,
On Fri, Feb 17, 2012 at 15:55, Leonardo Santagada <santagada@gmail.com> wrote:
why not statically link everything and mark the pre built binaries a "security risk" or whatever and then they will just work.
Anyone can either install PyPy from his own distribution, or translate it from sources; or attempt to get one of our nightly binary packages, which may or may not work because it's Linux. I think that this is what you get on Linux, and we will not try to find obscure workarounds (like making all our nightly binary packages twice as big just for this use case).
it would also make testing old nightly builds much easier, as they will just work on any machine with any openssl. Another option would be to do a semi-source distro, shipping the resulting c files and the makefile so people would still need to compile the sources but it would link to the openssl lib they have available or does the c files too specific to work? Is static linking really obscure? Just use xz instead of gz to compress the binaries and you will probably get most of the space back. It is far easier to find a xz binary then to find a machine with +/- 2 hours and 4gb of ram to build a pypy from source. -- Leonardo Santagada
Anyone can either install PyPy from his own distribution, or translate it from sources; or attempt to get one of our nightly binary packages, which may or may not work because it's Linux. I think that this is what you get on Linux, and we will not try to find obscure workarounds (like making all our nightly binary packages twice as big just for this use case).
Or you can just do what I did. Find a old package for your linux system and install that. On my Ubuntu box v11.10, I simply found a old openssl-0.9.8o.deb that was meant for version 10.x. The deps on the package stated something like: libc >= 2.4.3 So it just installed and ran fine. PyPy is now happily running on my machine. Timothy
On Mon, 2012-02-13 at 14:42 -0800, 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.
FWIW, I've built PyPy 1.8 in RPM form for RHEL 5 and 6, within the "EPEL" community repositories: http://fedoraproject.org/wiki/EPEL So if you've configured the EPEL repos, you can install pypy via: # yum install pypy and not have to do the translation yourself. Note that this is a side-project by me, not an "official" Red Hat-supported thing. The EPEL 5 builds of pypy 1.8 can be seen here: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0276 The EPEL 6 builds of pypy 1.8 can be seen here: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0275 Hope this is helpful Dave
Hi to all who answered me and thanks for the good assistance. I gave up on the binary distribution right off, and tried to build it from source on RHEL5. I had the most difficulty with the libffi part, I tried a server located directory, /usr/local, and finally /usr as my libffi installdir, but gave up finally with the key error being the ffi include file not being located. RHEL6 has this libffi library readily available to our installs, I may pursue an install from the source on RHEL6 instead, once I go over the pre-reqs. It worked fine with the existing SSL libraries as others posted, I did not need 0.9.8 at all. The absolute most help are the RPM's built by David Malcolm at EPEL, thanks so much for those. They installed well and I will place them in our satellite server for subsequent kickstarts. Our researchers have had a nice speedup with their python and are very eager to try it. So my next problem is that the users upped their request. They did not tell me they wanted particular modules also, such as numpy. I saw reference to numpypy and will look into that, I've not read any docs on installing pypy modules yet. I'm familiar with installing python modules already. I do have a question along those lines. We have a fileserver located python 2.7.2 and we install python modules into that location. When I am building pypy from the source I have been using that version of python. If I use that python and am successful at building pypy will users of my pypy have access to the python modules in that python install, or rather do I need to independently install all the modules pypy users want into the pypy filetree? i.e., Does pypy use the available python modules on the host, or does it need its own? thanks to all again, Dale On 02/21/2012 08:16 AM, David Malcolm wrote:
FWIW, I've built PyPy 1.8 in RPM form for RHEL 5 and 6, within the "EPEL" community repositories: http://fedoraproject.org/wiki/EPEL
So if you've configured the EPEL repos, you can install pypy via:
# yum install pypy
and not have to do the translation yourself.
Note that this is a side-project by me, not an "official" Red Hat-supported thing.
The EPEL 5 builds of pypy 1.8 can be seen here: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0276
The EPEL 6 builds of pypy 1.8 can be seen here: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0275
Hope this is helpful Dave
-- -- Dale Hubler dhubler@uw.edu (206) 685-4035 Senior Computer Specialist University of Washington Genome Sciences Dept.
Hi, Maybe we should write down some answers to these questions in a single place... On Thu, Feb 23, 2012 at 00:32, Dale Hubler <dhubler@uw.edu> wrote:
They did not tell me they wanted particular modules also, such as numpy.
'numpypy' is already included in a baseline PyPy but is only a partial implementation of numpy so far.
I do have a question along those lines. We have a fileserver located python 2.7.2 and we install python modules into that location. When I am building pypy from the source I have been using that version of python.
What we or you used to translate pypy (cpython 2.5-2.7 or pypy itself) has no effect on the result. You need to install everything for pypy independently, just like you need to install everything independently for various versions of CPython. The module installation is very similar to CPython's. It should mostly just work if you use PyPy instead of CPython to run the installer, e.g. "pypy setup.py install". If the module contains a C extension, it may or may not work out of the box. A bientôt, Armin.
participants (9)
-
Armin Rigo -
Bengt Richter -
Dale Hubler -
Dale Hubler -
David Malcolm -
Justin Bogner -
Leonardo Santagada -
Maciej Fijalkowski -
Timothy Baldridge