Skip to content
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

Building against static Python interpreter #458

Open
jakirkham opened this issue Nov 6, 2018 · 1 comment
Open

Building against static Python interpreter #458

jakirkham opened this issue Nov 6, 2018 · 1 comment

Comments

@jakirkham
Copy link
Contributor

If the Python interpreter is built statically on Unix, there is no need to link to the Python dynamic library (in fact it will cause segfaults). Vigranumpy (at least in the 1.11.1 release) still picks up the dynamic library during the build in this case, which causes problems. Would be good if it could either provide an option to disable use of the dynamic library or better yet detect static linkage and skip including the dynamic library. FWIW here's the workaround we used to bypass the dynamic library in conda-forge.

@stuarteberg
Copy link
Contributor

As I mentioned in conda-forge/vigra-feedstock#43 (comment), I have concerns about the proposed workaround. I think we should avoid -undefined dynamic_lookup if possible. I've had only negative experiences with that linker setting in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants