Date: Fri, 08 Aug 2014 17:51:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-python@FreeBSD.org Subject: [Bug 192511] [patch] fix lang/python27 build with libressl Message-ID: <bug-192511-17421-YgrLW2rCJt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192511-17421@https.bugs.freebsd.org/bugzilla/> References: <bug-192511-17421@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 --- Comment #4 from meyer.arne83@gmail.com --- (In reply to Marcus von Appen from comment #3) > (In reply to meyer.arne83 from comment #2) > > (In reply to Marcus von Appen from comment #1) [...] > > > 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. > > How about this: > > * Add smt. like WITH_OPENSSL_LIBRE and some logic to bsd.openssl.mk > > * Have the libressl port fail to build without that flag set. > > That sounds reasonable. I added the libressl maintainer and portmgr@ to this > issue to get their feedback on it. > I implemented the WITH_OPENSSL_LIBRE logic on my laptop. Tested it. Looks good so far. The only issue is: Are there ports who have a hard dependency on openssl/ports? > > * Add a static library or c file with dummy functions(RAND_egd, ...) to > > libressl. > > That might contradict the purpose of libressl and adds a can of worms (local > patches), which should be avoided. Best'd be to ask the upstream developers > of libressl about such things, I think. Yeah. You're right about that. I have a patch for libressl that adds back the RAND_egd api. But the functions just return -1 (means no connection to egd). As RAND_egd is the main reason for breakage, and basically useless, that seems like a tolerable approach to me. That way, we don't have to patch every user of that api. With that patch and the change to bsd.openssl.mk I can compile python27 without my first patch. I can open up a new bug with my patches, if anyone is interested... -- 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-17421-YgrLW2rCJt>