You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running cargo test --bin pyoxidizer --release, most tests fail due to it not finding the default Python distribution for armv7-unknown-linux-gnueabihf, apparently.
This is running on a Nintendo Switch running ArchLinuxARM, in an AArch32 chroot. I haven’t tested in AArch64 yet but I assume the outcome will be similar.
The text was updated successfully, but these errors were encountered:
The good news is that a bit of work has gone into python-build-standalone recently and its cross-compiling story is rapidly maturing. We have support for producing macOS aarch64 distributions now.
Unfortunately, we don't yet have support for Linux ARM devices. This is on my long list of things to get working. There is a PR against python-build-standalone that introduces cross-compiling ARM support. But it needs some work before it can merge.
If I could chat with someone who is knowledgeable about the state of cross-compiling on ARM, it might help move things along. I don't know basic things like what's considered the ideal Linux environment for cross-compiling. I see tools like https://github.com/dockcross/dockcross but don't know if these cross-compiling environments are considered production quality!
Here is the build log: pyoxidizer cargo test
When running
cargo test --bin pyoxidizer --release
, most tests fail due to it not finding the default Python distribution for armv7-unknown-linux-gnueabihf, apparently.This is running on a Nintendo Switch running ArchLinuxARM, in an AArch32 chroot. I haven’t tested in AArch64 yet but I assume the outcome will be similar.
The text was updated successfully, but these errors were encountered: