Matti Picus wrote:
> I have uploaded pypy3.5 v5.10.1 bug-fix release candidates to
> https://bitbucket.org/pypy/pypy/downloads please test them out.
>
> The sha256 hashes are available at the end of the source for the website
>
https://bitbucket.org/pypy/pypy.org/src/extradoc/source/download.txt
On 12/01/18 14:33, Neal Becker wrote:
Haven't tried pypy for some time, but just tried it on fedora 27.
pypy
pypy: error while loading shared libraries: libbz2.so.1.0: cannot open
shared object file: No such file or directory
I d/l pypy3-v5.10.1-linux64.tar.bz2 and installed locally.
_
Matti Picus wrote:
>
>
> On 12/01/18 14:33, Neal Becker wrote:
>> Haven't tried pypy for some time, but just tried it on fedora 27.
>> pypy
>> pypy: error while loading shared libraries: libbz2.so.1.0: cannot open
>> shared object file: No such file or directory
>>
>> I d/l pypy3-v5.10.1-linux64
Neal Becker wrote:
> Matti Picus wrote:
>
>>
>>
>> On 12/01/18 14:33, Neal Becker wrote:
>>> Haven't tried pypy for some time, but just tried it on fedora 27.
>>> pypy
>>> pypy: error while loading shared libraries: libbz2.so.1.0: cannot open
>>> shared object file: No such file or directory
>>
Hi Neal,
On 12 January 2018 at 20:35, Neal Becker 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