-
Notifications
You must be signed in to change notification settings - Fork 88
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
No supported wheels found for macOS arm64 #457
Comments
OK, the solution I have found for now is to skip tests for arm64, so in my azure template in the install wheel and test:
That produces wheels for macos 11 (As I set the MACOSX_DEPLOYMENT_TARGET to 11.0) which seem to work well. It would be of course be better to have the tests in place. If I understand correctly, what is happening here is that in my job matrix I have MB_PYTHON_OS_VER set to 10.9, and probably that old python doesn't recognize the wheel for osx 11. I tried to set the MB_PYTHON_OS_VER to 11, but that fails because multibuild is naming the python package to be downloaded incorrectly:
when the package is named python-3.8.10-macos11.0.pkg (not macosx, the x is not needed, see here, so it seems to me that multibuild needs adaptation at that point. |
Should be fixed by #528 and others. Closing, please reopen or open a new issue if the problem persists. |
hi
I am trying to build macOS arm64 wheels for my project on Azure pipelines, but this specific platform is failing (default MacOS and linux are fine) is failing during tests (building is succeeding) with the error:
I tried to do something similar as this one, but didn't manage: https://github.com/MacPython/scipy-wheels/pull/150/files
What am I doing wrong?
Here is my azure yml: https://github.com/ofajardo/pyreadr_wheels4/blob/master/azure-pipelines.yml
and here the azure pipelines failing: https://dev.azure.com/ofajardo/pyreadr_wheels4/_build/results?buildId=105&view=logs&j=edc54a0e-92d1-574b-433e-80fdfaa23be3&t=d0e4c54a-7f31-5215-670d-55d58cc754a5&l=51
thanks in advance for the help!
The text was updated successfully, but these errors were encountered: