Date: Wed, 04 Nov 2015 10:19:54 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 199050] lang/python34: Fix build with LibreSSL without NLS Message-ID: <bug-199050-21822-pk4EpI7e80@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199050-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-199050-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=199050 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(python |maintainer-feedback+ |@FreeBSD.org) | Keywords| |needs-qa Status|In Progress |Open --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- Unconditionally setting this in LIBS is too widely scoped, and likely to pollute the build by detecting, building against and link other (unwanted) libraries implicitly. This is one of the reason why its currently only scoped to the NLS option. Either the fix needs to be scoped to SSL detection only, either in ./configure or otherwise, and needs to support and be compatible with all of the following the following three cases: For all lang/python* ports (since this is presumably reproducible in all of them) - OpenSSL in base - OpenSSL from ports - LibreSSL from ports My gut feeling tells me that the best way to address this is with openssl specific include/library arguments in ./configure, which are then passed to setup.py (for extensions), OR Playing with ssl_incs and ssl_libs variables (and contents) might also be an avenue, similar to what setup.py does for readline and dbm (dbmliborder): -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199050-21822-pk4EpI7e80>