-
Notifications
You must be signed in to change notification settings - Fork 44
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
BUG: cannot handle __osx>=11.0
on osx-arm64?
#1052
Comments
Ah, interesting! If this is executing on osx-64 then this should work (ie. if there is no cross-compilation going on). But this is going to be easy to reproduce. Maybe we're missing teh virtual package injection when creating test envs. Thanks! |
Sorry, perhaps the issue title was misleading. I'm talking about cross-compilation from osx-64 to osx-arm64, not native compilation. |
Is it supposed to run the tests? I think not and I think we need a conda-smithy release to fix it for the rattler-build case. |
No, it isn't supposed to run the tests (we have no emulation, so it would necessarily fail). However, I'm already using a dev install of smithy, and something doesn't seem to be dealing with |
I might be seeing the same issue at conda-forge/xformers-feedstock#33 (comment) |
I have a PR that would print the virtual packages. Thanks for testing @hadim - it's super helpful 🙏 |
No problem! The issue only appears on the cf Azure CI. Do you know an easy way to test a custom rattler-build binary (from your PR) within Azure directly? (without hacking too much, the script files) |
Unfortunately no. Will cut a release shortly |
This was a vicious bug thanks to Apple - the system Thanks to @beckermr for digging deeply and @baszalmstra for remembering something about |
Not really sure where the right place to raise this issue is, perhaps we also need to do something in smithy or conda-forge CI. However, given that conda-build works for this, I'm starting here.
As another issue from conda-forge/zlib-feedstock#83, osx-arm64 builds are failing with:
The images are macOS-12, so we should be satisfying
__osx>=11.0
easily.The text was updated successfully, but these errors were encountered: