Closed mattip closed 2 years ago
Do you see this on the main branch?
Yes, with PyPy3.8 commit ee93f9f13 fails as well.
Hmm, doing the following succeeded. I will close this and try to figure out what went wrong with my original effort.
git clone https://github.com/pyca/pynacl
wget https://downloads.python.org/pypy/pypy3.7-v7.3.6rc3-linux64.tar.bz2
tar -xf pypy3.7-v7.3.6rc3-linux64.tar.bz2
pypy3.7-v7.3.6rc3-linux64/bin/pypy -m ensurepip
pypy3.7-v7.3.6rc3-linux64/bin/pypy -m pip install wheel
cd pynacl
../pypy3.7-v7.3.6rc3-linux64/bin/pypy setup.py bdist_wheel
For future reference: one difference seems to be that CC='gcc'
where it succeeds, and CC='gcc -pthread'
where it fails.
may we have a wheel for PyPy 3.8 on Windows ?
I think this project releases limited API wheels, like PyNaCl-1.4.0-cp35-abi3-win_amd64.whl
that can work on any cpython 3.5+. PyPy does not yet have limitedAPI wheel support, even for cffi-based projects. See issue https://foss.heptapod.net/pypy/pypy/-/issues/3327. FWIW, you can get pynacl=1.4.0 via conda for pypy3.7 + windows.
Any thoughts why
python -m pip wheel .
fails to successfully run the configure script for libsodium on 1.4.0 but does run it on 1.3.0? Here is a snippet, and the complet configure.log is in the detailsI am not sure how to capture the config.log for a successful build for comparison.