-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Builds do not work for Apple M1 target in GitHub Actions #566
Comments
oh it should be for
for
|
The first error seems to show us attempting to execute a Mach-O binary on Linux. The second seems to show us attempting to execute an ELF binary for a foreign CPU type. This points to a bug where we're not detecting the host target correctly and attempting to run the wrong Python distribution. This should just work in modern versions of PyOxidizer. I think a potential problem here might be the |
Same after changing to |
I think maybe the issue here is you are running under ARM QEMU on Linux. What might be happening is PyOxidizer doesn't recognize the current host target and falls back to attempting to use an x86_64-unknown-linux-gnu Python distribution since an aarch64-unknown-linux-gnu distribution isn't available. I'll try to push code today that adds the aarch64-unknown-linux-gnu distributions to PyOxidizer. |
Still not yet working, using artifacts from https://github.com/indygreg/PyOxidizer/actions/runs/2416005657:
|
I'm still perplexed why we're getting an But if you want to build for Apple M1, you should build from a macOS GitHub Actions runner for best results. In theory cross-compilation from Linux to macOS is supported. In reality, it requires a lot of manual muckery. It isn't well documented and very brittle. I recommend using macOS to build for macOS. |
Oh I thought ARM emulation was required. Do you have an example? |
Here's a repo you can fork to test it not working https://github.com/ofek/pyoxidizer-build-example Latest build failing for M1 https://github.com/ofek/pyoxidizer-build-example/actions/runs/2431461199 |
Any ideas? |
This is due to the use of Essentially, today Workaround is to use PyOxidizer should absolutely have better documentation and error reporting around this footgun. |
Ah okay thanks. So how would one install the current package? I think |
I can confirm ^ does not include the current package. Additionally, it seems v0.21.0 broke builds on macOS GitHub Actions runners e.g.
|
That
You may want the |
Filed #585 for the liblzma issue. |
The text was updated successfully, but these errors were encountered: