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
Please link modules with shared lib #39475
Comments
We've been working with libraries that are loaded with Due to the behavior of the dynamic linker, this would The main executable isn't linked with python, and none The dlopened library is linked with python. However, If each module had a NEED for the python lib (via -l at I've got some local patches to build_ext.py for this |
Logged In: YES Please do provide patches. Take into account that modules |
Logged In: YES To turn my patches into things that anyone else would want, |
Logged In: YES You can probably rely on libpythonxy.so ending up in |
Logged In: YES I'm running into issues trying to come up with a clean version
I have this feeling that someone had a plan here that I'm too |
Logged In: YES
|
Logged In: YES I submitted a set of patches that work for the initial build. I |
Logged In: YES I only see one possible issue with the patch. I exploited the existing BLDLIBRARY macro. It says '-L.' on The comments in the config dir leave me thinking that there The RUNSHARED macro ends up set back to where I built it, |
Logged In: YES See patch bpo-1429775. |
Logged In: YES This was fixed with said patch in r45232. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: