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
Full output from the second cargo test call (80 KiB): full-output.txt
The same tests pass on all other architectures I've tried. I'm filing a bug here since this is the package I'm seeing it with. CC @davidhewitt from PyO3.
The text was updated successfully, but these errors were encountered:
FWICS it causes PyO3 to assume it's compiling a Python extension and therefore not link to libpython*.so explicitly — which means the Python symbols PyO3 is trying to use doesn't get resolved.
The true mystery is why it doesn't fail on amd64. My educated guess is that some optimization pass removes all Python library calls there, while they still do happen on PPC.
Thanks for the ping - yes, the extension-module feature is a longstanding pain because while it makes for technically correct extension module builds it breaks all executables and tests as part of the same project. I have an idea for an alternative which would be much more user friendly which I hope I might land in the next version of PyO3.
As for why the link failures are architecture specific, that's a surprise to me too. Possibly some cargo config which overrides the linking?
As for why the link failures are architecture specific, that's a surprise to me too. Possibly some cargo config which overrides the linking?
If you're referring to project-specific or system-specific config, then no. The project is as simple as it gets, and the system is pretty much vanilla. If anything, it would have to be something upstream in the Rust distribution itself.
Honestly, I don't know what to make of this.
Full output from the second
cargo test
call (80 KiB): full-output.txtThe same tests pass on all other architectures I've tried. I'm filing a bug here since this is the package I'm seeing it with. CC @davidhewitt from PyO3.
The text was updated successfully, but these errors were encountered: