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

Shouldn't pythonXX/config contain symlink to libpythonXX.so ? #1295

Open
Micket opened this issue Nov 21, 2017 · 0 comments
Open

Shouldn't pythonXX/config contain symlink to libpythonXX.so ? #1295

Micket opened this issue Nov 21, 2017 · 0 comments

Comments

@Micket
Copy link
Contributor

Micket commented Nov 21, 2017

I've seen at least one application (GPAW) needlessly statically link to libpython*.a due to it adding -Lpath/to/pythonXX/config.
This, in turn, is causing me problems to build applications due to #1068 (whereas the shared library links fine).

While, it's certainly not the nicest build scripts that starts mucking about in distutils.sysconfig.get_config_vars(), I have had a hard time finding out who is "wrong" in this situation.
For example on my debian machine, python-config --ldflags does point to the lib/pythonXX/config/ directory, which indicates to me that it is indeed meant to be used. On debian, this path also contains a symlink to libpythonXX.so.
This at least indicates that this is, on some platforms, somewhat normal linking behavior.

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

1 participant