Summary: | dev-python/pypy3 and dev-python/pypy3-bin - sharedctypes: global name 'buffer' is not defined | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | genoob |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | genoob, mgorny, python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info pypy3-bin
tests with pypy-c-jit-90367-4618cb6fc961-linux64 and /usr/bin/pypy3 test with pypy3 built locally from pypy3.5 branch from https://bitbucket.org/pypy/pypy |
Description
genoob
2017-02-27 14:30:10 UTC
Created attachment 465416 [details]
tests with pypy-c-jit-90367-4618cb6fc961-linux64 and /usr/bin/pypy3
Testing with the vanilla build from pypy3 repository vs pypy3-bin from gentoo repository. (I'm using bin currently because it's quicker to test, but I have also tried both versions of pypy3 from source and they also failed.
EBUILD keyword is for bugs which include fixed ebuilds ;-). And we don't really use keywords much, so don't bother setting them. As for this issue, I'll try to look at it in a few days. However, I can't promise you much since PyPy is a very complex thing. I don't think we really do anything around the build that could cause this -- which is more likely to be a generic problem when building on Gentoo. If you have resources to test this, you can try building PyPy locally and seeing if it works. Created attachment 465930 [details] test with pypy3 built locally from pypy3.5 branch from https://bitbucket.org/pypy/pypy I have already done that too. I cloned the repository and built the py3.5 branch, test passed. Could you retry with 5.9.0? It succeeds (from -bin) on my system. |