Date: Fri, 08 Aug 2014 12:55:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192511] [patch] fix lang/python27 build with libressl Message-ID: <bug-192511-13-iLF1P8NvDm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192511-13@https.bugs.freebsd.org/bugzilla/> References: <bug-192511-13@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=192511 Marcus von Appen <mva@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |In Discussion URL| |http://bugs.python.org/issu | |e21356 CC| |mva@FreeBSD.org --- Comment #1 from Marcus von Appen <mva@FreeBSD.org> --- Root problem: As soon as libressl is installed via ports, lang/pythonXX and other ports will try to pick it up, most likely due to the include and linker flags order. This is problematic in two regards: * lang/python27 does not have an explicit BUILD/RUN_DEPENDS on libressl, since libressl is not officially supported by upstream (yet) * libressl is API and ABI incompatible with OpenSSL, so depending on the system status (libressl installed or not), python will take the one or other. I do not like the patch, since it would disable the function for both, OpenSSL and libressl and thus effectively change the behaviour of lang/pythonXX. We need to get two things right: * handle OpenSSL support correctly and explicitly use OpenSSL, so that an installed SSL replacement does not cause a wrong and unintended behaviour * offer users to link against libressl explicitly (via an OPTION), which can cause different behaviour. -- 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-192511-13-iLF1P8NvDm>