Date: Fri, 11 May 2018 08:54:07 +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-CcaZkD8Vq0@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227939 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bapt@FreeBSD.org Status|New |Open Keywords| |needs-qa See Also| |https://github.com/osmcode/ | |pyosmium/issues/55 Flags|maintainer-feedback?(python |maintainer-feedback+ |@FreeBSD.org) | --- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> --- Hi Jan, apologies for the delay. See Also: (1) https://bugs.python.org/issue23817 (remove freebsd SOVERSION special case) (2) https://github.com/osmcode/pyosmium/issues/55 (origin of this issue) (3) https://bugs.python.org/issue1610795 (original freebsd find_library python code) (1) ended up in only 3.5+, though I requested a backport to 3.4 and 2.7 so the behaviour was consistent in all versions. This explains the discrepancy between Python versions in comment 2. CC'ing bapt@ here too for opinions/thoughts, he originated the issue and patch upstream. We could backport it ourselves, and/or add symlink in the python ports, and/or modify the SOVERSION/INSTSONAME for the python port builds, *but* we'd like to avoid doing so if the better/correct/permanent/rootcause resolution is elsewhere. Correct me if my reading is off, but it sounds like we have the following options/paths, or combination thereof, so that we can have all supported freebsd/python versions work out of the box. - Fix ports that don't install symlinks to do so - Fix python ctypes/find_library to be correct/great on all FreeBSD versions. - Fix ldconfig something something in the absence of symlinks / other condition(s). Are some/all of the above what you referred to when you mentioned a workaround? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227939-21822-CcaZkD8Vq0>