[Bug 227939] devel/boost-python-libs vs ctypes.util.find_library
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon May 14 17:03:08 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227939
--- Comment #4 from Wiktor Niesiobedzki <bsd at vink.pl> ---
I agree on the possible options laid out by koobs at .
I didn't found any relevant documentation for FreeBSD, but there is something
for Linux:
http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html
It specifies, that:
lib<NAME>.so.<MAJOR>
Is a fully-qualified soname for library and ldconfig is responsible (at least
on Linux) on setting the link to library realname (in this case -
libboost_python%%PYTHON_SUFFIX%%.so.%%BOOST_SHARED_LIB_VER%%), while
libboost_python%%PYTHON_SUFFIX%%.so is only a linker name - used during
compilation, not during library load.
I'm not sure if FreeBSD follows the same convention for ldconfig, but if so,
then either ldconfig or install scripts should ensure that fully-qualified
soname is created for installed library. So I lean more towards that's
multiple-port issue or base system issue.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
More information about the freebsd-python
mailing list