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
Rust binding in 3.4+ dynamically links with non-existent library #5807
Comments
Could you please clone the bug to https://github.com/PyO3/setuptools-rust? All magic happens inside the setuptool_rust package. |
Thanks, done: PyO3/setuptools-rust#106 |
The 3.4.6 release still has this problem because |
Looks like there’s going to be a setuptools-rust release in the next few days which will resolve this. |
The wheel for macOS includes _rust.abi3.so. This references a library that isn't shipped and has a path clearly from the build machine:
Whilst this may not break the package, it:
A) Is not good practice
B) Breaks build systems that automatically fixup library paths when creating relocatable appbundles.
B is the issue I'd like to see fixed, as the current situation requires me to modify code that's worked for many years (15+) to ignore errors when processing this particular file.
An additional issue, again likely benign for the general use case, is that _rust.abi3.so does not have the executable bit set as is generally the norm for shared libraries on *nix platforms. This also required me to change build code, as searches for binaries that need to be codesigned filtered possibly targets based on the executable bit, before doing further tests to see if the file was actually an executable or library (which gets very expensive without that check, in a codebase with thousands of Python/JS/HTML files etc).
Probably not relevant, but here's my system info:
Thanks!
The text was updated successfully, but these errors were encountered: