Date: Mon, 14 May 2018 17:03:05 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227939] devel/boost-python-libs vs ctypes.util.find_library Message-ID: <bug-227939-21822-48IRh3Jyfv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227939-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-227939-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227939 --- Comment #4 from Wiktor Niesiobedzki <bsd@vink.pl> --- I agree on the possible options laid out by koobs@. I didn't found any relevant documentation for FreeBSD, but there is somethi= ng 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 lea= st 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. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227939-21822-48IRh3Jyfv>