@@ -67,10 +67,12 @@ AC_SUBST(python_includespec)[]dnl
6767# directory name and LDLIBRARY is the file name of the shlib. But in older
6868# installations LDLIBRARY is frequently a useless path fragment, and it's also
6969# possible that the shlib is in a standard library directory such as /usr/lib
70- # so that LIBDIR is of no interest. We must also check that what we found is
71- # a shared library not a plain library, which we do by checking its extension.
72- # (We used to rely on Py_ENABLE_SHARED, but that only tells us that a shlib
73- # exists, not that we found it.)
70+ # so that LIBDIR is irrelevant. Also, some packagers put the .so symlink for
71+ # the shlib in ${python_configdir} even though Python itself never does.
72+ # We must also check that what we found is a shared library not a plain
73+ # library, which we do by checking its extension. (We used to rely on
74+ # Py_ENABLE_SHARED, but that only tells us that a shlib exists, not that
75+ # we found it.)
7476AC_DEFUN ( [ PGAC_CHECK_PYTHON_EMBED_SETUP]
7577[ AC_REQUIRE ( [ _PGAC_CHECK_PYTHON_DIRS] )
7678AC_MSG_CHECKING ( [ how to link an embedded Python application] )
9496fi
9597# Search for a likely-looking file.
9698found_shlib=0
97- for d in "${python_libdir}" /usr/lib64 /usr/lib; do
99+ for d in "${python_libdir}" "${python_configdir}" /usr/lib64 /usr/lib
100+ do
98101for e in .so .dll .dylib .sl; do
99102if test -e "$d/lib${ldlibrary}$e"; then
100103python_libdir="$d"