[pypy-issue] Issue #2646: s390x and ppc64le releases link to "libssl.so.10" instead of "libssl.so.1.0.0" (and libcrypto) (pypy/pypy)

Tianon Gravi issues-reply at bitbucket.org
Wed Sep 6 17:53:05 EDT 2017


New issue 2646: s390x and ppc64le releases link to "libssl.so.10" instead of "libssl.so.1.0.0" (and libcrypto)
https://bitbucket.org/pypy/pypy/issues/2646/s390x-and-ppc64le-releases-link-to

Tianon Gravi:

I'm maintaining Docker images for `pypy`, and consuming the officially released binary tarballs (https://github.com/docker-library/pypy). :heart:

For all of `linux64`, `linux-armel`, `linux-armhf-raring`, and `linux32`, the `pypy` binary links to `libssl.so.1.0.0` and `libcrypto.so.1.0.0` (which are both available in Debian and Ubuntu), but for `s390x` and `ppc64le`, the links are instead to `libssl.so.10` and `libcrypto.so.10` (which do not exist in either Debian or Ubuntu).

Is this intentional, or simply an oversight in how those architecture's artifacts are being built?  I tried simply symlinking the `.so` files, but then I get the following errors presumably due to the version of OpenSSL that `pypy` was compiled against:

```
pypy: /usr/lib/s390x-linux-gnu/libssl.so.10: version `libssl.so.10' not found (required by /usr/local/bin/libpypy-c.so)
pypy: /usr/lib/s390x-linux-gnu/libcrypto.so.10: version `OPENSSL_1.0.1_EC' not found (required by /usr/local/bin/libpypy-c.so)
pypy: /usr/lib/s390x-linux-gnu/libcrypto.so.10: version `libcrypto.so.10' not found (required by /usr/local/bin/libpypy-c.so)
```

I'm happy to help do further debugging or even send a PR if someone can give me some pointers! :sweat_smile:

Thanks for your work!




More information about the pypy-issue mailing list