Detect compiling from Linux gnu to Linux musl as cross compiling #2010
Conversation
✅ Deploy Preview for maturin-guide ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Probably this was because Windows 32/64bit and macOS arm/x86_64 are somewhat special cases. I wonder whether the logic is backwards though, something to check in PyO3. |
|
EDIT: rereading, I think my comment above is not relevant. As far as I was concerned in PyO3 my thinking what that cross compiling is "can't run the target interpreter to discover config". I think Linux gnu systems can run musl binaries (but maybe only if the musl binary is statically linked?) |
Yeah, I think currently the only major player is Alpine Linux which is dynamically linked musl libc. |
https://build.opensuse.org/request/show/1178629 by user mia + anag+factory - Update to 1.6.0 * Add pypi name validation gh#PyO3/maturin#2007 * Add JSON schema generation gh#PyO3/maturin#2005 * Detect compiling from Linux gnu to Linux musl as cross compiling gh#PyO3/maturin#2010 * Upgrade uniffi to 0.27.0 gh#PyO3/maturin#2021 * Add instrumentation support for develop gh#PyO3/maturin#2019 * Make tracing-subscriber mandatory gh#PyO3/maturin#2022 * Import hook upgrade gh#PyO3/maturin#2024 * Add uv as develop backend command gh#PyO3/maturin#2015 * Also try uv in PATH in develop --uv gh#PyO3/maturin#2026 * docs: update pyo3 to match tutorial gh#PyO3/maturin#2029 * Add support for AIX gh#PyO3/maturin#2030 * Remove rust-cpython from project init/new template gh#PyO3/maturin#2034 * Only run uv tests
The original code logic was derived from pyo3, I don't remember why it does not consider cross-compiling if arch-vendor-os is all the same.
For maturin to correctly use bundled sysconfig Python when compiling from Linux gnu host to Linux musl target, we need to detect it as cross compiling, otherwise it will only find Python interpreters on the host that was compiled for glibc.
cc @davidhewitt