On 13/01/18 00:03, Armin Rigo wrote:
Hi Neal,
On 12 January 2018 at 20:35, Neal Becker <ndbeck...@gmail.com> wrote:
So Fedora has libbz2.so.1 and libbz2.so.1.0.6, but no libbz2.so.1.0. In
fact, isn't depending on libbz2.so.1.0 an error?
Unless I'm mistaken, it's what we get from ``gcc -lbz2`` on Ubuntu.
If you think doing so gives a dependency that is erroneous, then the
problem is either inside gcc or Ubuntu, not PyPy.
In general, taking a binary compiled for Linux distribution X and
trying to use it in Linux distribution Y only works if the stars are
correctly aligned. This is known and documented in
http://pypy.org/download.html#linux-binaries-and-common-distributions
A bientôt,
Armin.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561175,
confirming what Armin said - this is a Debian/Ubuntu issue, and AFAICT
only should affect libbz2.
The "solution" for the RPM-based users would be to manually create the
symbolic link, or to use the portable builds.
Matti
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
