Date: Sun, 15 Jul 2018 13:31:31 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 229119] lang/ruby25: OpenSSL broken Message-ID: <bug-229119-21402-bG3PEwjOvJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229119-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-229119-21402@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=229119 Thibault Jouan <tj+freebsd_ports@a13.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tj+freebsd_ports@a13.fr --- Comment #1 from Thibault Jouan <tj+freebsd_ports@a13.fr> --- Created attachment 195147 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195147&action=edit Fix openssl ext behavior with OpenSSL 1.0 This patch should fix runtime behavior with both OpenSSL from base and from security/openssl port (broken since ports r465590, bug #226852). Current status, without this patch: ssl=base runtime behavior is broken ssl=openssl runtime behavior is broken ssl=openssl-devel does not build ssl=libressl OK ssl=libressl-devel OK After applying the patch: ssl=base OK ssl=openssl OK ssl=openssl-devel does not build ssl=libressl OK ssl=libressl-devel OK I'm not sure yet why I can't build against openssl-devel, but I've been using this patch with ssl=openssl since a few months and didn't notice any particular problem. I just checked again that it still allow building with ssl=libressl-devel, and seems to run fine. -- 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-229119-21402-bG3PEwjOvJ>