-
Notifications
You must be signed in to change notification settings - Fork 802
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
failed to open PyO3 config file at pyo3-cross-compile-config.txt
in manylinux2010 docker container
#2229
Comments
pyo3-cross-compile-config.txt
pyo3-cross-compile-config.txt
in manylinux2010 docker container
It seems that the failure only occurs when host is x86_64 and the target is x86_64 or i686. https://github.com/messense/maturin-action/actions/runs/1990613199 I guess pyo3-build-config determines it's not cross compiling when |
Does #2232 fix it? Looks like we should always make the checks only if none of the environment variables are set. |
I would have expected that the check in https://github.com/PyO3/pyo3/blob/main/pyo3-build-config/src/lib.rs#L73 which is only looking the environment variables would need the same checks for the various target combinations? |
Ah, this makes sense if setting those variables is supposed to force cross-compilation unconditionally? |
I think that check is correct - the cross compile config should always exist when the environment variables are set, yes. The problem is that we seem to be not doing this in some cases. |
Bug Description
After #2224 it still fails with the same kind of error message on Linux.
Steps to Reproduce
https://github.com/messense/maturin-action/runs/5563946271?check_suite_focus=true
Run the following command in manylinux2010 docker image on pyo3-mixed test crate:
Backtrace
Your operating system and version
Ubuntu 20.04
Your Python version (
python --version
)Python 3.8
Your Rust version (
rustc --version
)1.59.0
Your PyO3 version
0.16.2
How did you install python? Did you use a virtualenv?
from manylinux2010 docker image.
Additional Info
No response
The text was updated successfully, but these errors were encountered: