-
Notifications
You must be signed in to change notification settings - Fork 59
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
This function does not support separate values per-architecture: 'i386' #153
Comments
I had to put them side-by-side to understand: { 'i386': [('/opt/X11/lib/libSM.6.dylib', '7.0.0', '7.1.0'), ('/opt/X11/lib/libICE.6.dylib', '10.0.0', '10.0.0'), ('/usr/lib/libSystem.B.dylib', '1.0.0', '1252.50.4')],
'x86_64': [('/opt/X11/lib/libSM.6.dylib', '7.0.0', '7.1.0'), ('/opt/X11/lib/libICE.6.dylib', '10.0.0', '10.0.0'), ('/usr/lib/libSystem.B.dylib', '1.0.0', '1311.120.1')],
'arm64': [('/opt/X11/lib/libSM.6.dylib', '7.0.0', '7.1.0'), ('/opt/X11/lib/libICE.6.dylib', '10.0.0', '10.0.0'), ('/usr/lib/libSystem.B.dylib', '1.0.0', '1311.120.1')]} I personally wasn't expecting a lib with all three architectures, although I probably should have, and it's clear that ignoring I'm not sure what would be best here. Based on your workaround, maybe allowing the I don't have the tools to make a proper test for this, and my setup doesn't make it easy to make contributions either. At most I could approve a PR. In your case you could upload your workaround to a personal branch and tell Pip to install delocate from that. |
Thanks @HexDecimal , I will try to find some time next week to do a PR. |
There's no simple workaround. All functions calling The CI tests for Decloate were running on older software, but adding |
Thanks. I deleted my post, since I realized the problem might not be entirely in delocate. When I build wheels on my local machine they get built for |
No, you were correct. This is an issue with Delocate. Specifically that Delocate hasn't yet been updated to correctly handle how the newer macOS tools treat libraries with multiple architectures. In the future, do not hastily delete your posts. It's better for a repo maintainer to hide your post if it turns out to be irrelevant. If you're using GitHub Actions then you could workaround the issue by using an older runner. |
I don't actually want a multi-architecture wheel. It already uses libraries that are single architecture, so really I just want an arm64 wheel. Then I'll do a separate build on So now I'm digging through the source code for |
The platform version number should be as low as possible because wheels are forward compatible. |
I'm not using cibuildwheel. I was using the python installed with actions/setup-python. I just switched to micromamba and that gets the architecture right. Hopefully it won't cause any compatibility problems (since cibuildwheel uses the python.org versions). |
Describe the bug
running delocate-wheel for an
arm64
-only wheel withuniversal2
python installation:To Reproduce
Expected behavior
delocate-wheel works
Wheels used
Attaching here.
Manual:
Install
universal2
Python 3.8.10 from Python.org ; XQuartz fromxquartz.org
(this installs to/opt/X11
where the issue is manifesting from)To create the wheel:
Platform (please complete the following information):
Additional context
If I pop the
'i386'
from the dict passed to_check_ignore_archs
it works.wheel.zip
The text was updated successfully, but these errors were encountered: