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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: