-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pip makes an incompatible wheel (aarch64) #9980
Comments
So in short, upon (successfully) installing numpy, pip is creating a
|
Pip only consumes and does not build the wheel. You need to report to pypa/wheel instead. |
@uranusjr would you re-open if I changed the title to "pip doesn't recognize system-compatible wheel"? $ uname -m
aarch64 Wheel seems to be appropriately building an |
Can you post the result of the following?
pip does recognise 64-bit ARM, but your compatible tag output seems to suggest Python is reporting itself as 32-bit binary (cross-compiled), not 64-bit. |
Good call. I forgot that even when running a 64b kernel that Raspbian still uses a 32b userland; that's likely the problem, and you're correct it's a wheel issue. Thanks for pointing me in the right direction. (.venv) $ python -c 'import sys; print(sys.version); print(sys.maxsize == 2**31 - 1)'
3.9.4 (default, Apr 28 2021, 22:29:59)
[GCC 8.3.0]
True Looks like a relevant issue is |
For future readers / searchers, as a quick fix, I was able to convince |
Description
I'm running a raspberry pi on the 64 bit kernel and running into odd behavior when installing a local numpy wheel that was created as part of a previous install.
It seems that pip creates a wheel for aarch64, but then reports that this is incompatible with
pip debug --verbose
.Expected behavior
The wheel created during
pip install
should be installable.pip version
21.1.1
Python version
3.9.4
OS
Raspbian Buster on 64 bit kernel (armv8)
How to Reproduce
See above
Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: