Date: Mon, 16 May 2016 17:00:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209523] [www/squid]: building crashes on undefined reference to `SSL_set_alpn_protos' Message-ID: <bug-209523-13-AT0iQiQ6Jj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209523-13@https.bugs.freebsd.org/bugzilla/> References: <bug-209523-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=3D209523 --- Comment #4 from emz@norma.perm.ru --- Doesn't look so. Squid is behaving just fine when there's only one instance= of openssl, and one instance of openssl is, actually, a supposed environment. = What should be the behaviour of the linker when there are more than one instance= s - this is entirely the linker and the userland problem. So this is FreeBSD is= sue, and ports in particular. May be not the issue of the certain port, but definitely not the issue of squid. By the way, today I've also discovered that net/asterisk11 and net/asterisk= 13 just dump core when there's openssl 1.0.2 from ports installed along with b= ase openssl 1.0.1t. So this is may be the problem of the openssl port too. --=20 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-209523-13-AT0iQiQ6Jj>