fix libpypy-c.so needing certein versions
I have been trying to install PyPy locally for the last 3 days. I didn't have Openssl, which install fine. But then PyPy started not liking the new version (libssl.so.1.0.1), so I got the archive for 1.0.0, and installed. But then PyPy didn't like that the .so files didn't have to correct version name in them. [katelyn@anthill bin]$ ./pypy ./pypy: /home/katelyn/lib/libssl.so.1.0.0: version `OPENSSL_1.0.1' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) ./pypy: /home/katelyn/lib/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) ./pypy: /home/katelyn/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) ./pypy: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) ./pypy: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) It took me a day to find the hack here: http://stackoverflow.com/questions/18390833/no-version-information-available Although I had to put both OPENSSL_1.0.0 and OPENSSL_1.0.1in the file. Now I have to go build my own libc.so since libpypy.so doesn't like the one I have. [katelyn@anthill openssl-1.0.0s]$ pypy /home3/katelyn/opt/pypy2-v5.3.0-linux64/bin/pypy: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) /home3/katelyn/opt/pypy2-v5.3.0-linux64/bin/pypy: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /home/katelyn/opt/pypy2-v5.3.0-linux64/bin/libpypy-c.so) -- -katelyn
Hi, On 22 June 2016 at 03:08, Katelyn McNair <deprekate@gmail.com> wrote:
I have been trying to install PyPy locally for the last 3 days. I didn't have Openssl, which install fine. But then PyPy started not liking the new version (libssl.so.1.0.1), so I got the archive for 1.0.0, and installed.
But then PyPy didn't like that the .so files didn't have to correct version name in them.
I'm unsure what solution you propose. This is a known issue with binary distributions on Linux. You're trying to use on Linux distribution X a binary file that was made for distribution Y. It can't work cleanly. http://pypy.org/download.html#linux-binaries-and-common-distributions A bientôt, Armin.
On 22 June 2016 at 18:19, Armin Rigo <arigo@tunes.org> wrote:
http://pypy.org/download.html#linux-binaries-and-common-distributions
The portable builds linked from that page work really well if you're on a gnu/linux (thanks, squeaky!) - try those out first. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement.
Here is portable pypy. https://github.com/squeaky-pl/portable-pypy You can just use it by directly unzipping and running it. it comes with a virtual-env directly too. Regards, Phyo. On Wed, Jun 22, 2016 at 3:00 PM William ML Leslie < william.leslie.ttg@gmail.com> wrote:
On 22 June 2016 at 18:19, Armin Rigo <arigo@tunes.org> wrote:
http://pypy.org/download.html#linux-binaries-and-common-distributions
The portable builds linked from that page work really well if you're on a gnu/linux (thanks, squeaky!) - try those out first.
-- William Leslie
Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
participants (4)
-
Armin Rigo -
Katelyn McNair -
Phyo Arkar -
William ML Leslie