Date: Tue, 31 Mar 2015 12:08:57 -0700 From: Yuri <yuri@rawbw.com> To: freebsd-emulation@freebsd.org Subject: Re: VirtualBox (sometimes) not starting/hanging after recent openssl updates Message-ID: <551AF0C9.7090903@rawbw.com> In-Reply-To: <alpine.BSF.2.20.1503301546360.73240@wonkity.com> References: <20150329182732.GA1415@elch.exwg.net> <5519AF03.1030808@kit.bg> <20150330202151.GA1418@elch.exwg.net> <20150330173027.2207c592@Papi> <alpine.BSF.2.20.1503301546360.73240@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/30/2015 14:49, Warren Block wrote: > > Mine links only to 8, but does not work: > > /usr/local/lib/virtualbox/VBoxRT.so: > ... > libssl.so.8 => /usr/local/lib/libssl.so.8 (0x80244d000) People who have both libssl.so.8 and libssl.so.7 from both openssl port and base have libssl.so.7 from base coming through libcurl.so (run ldd -a to see this). Some update to curl during March caused curl to link to base when openssl port is requested there. Rolling curl back to Mar 1 version removes libssl.so duplicate, but doesn't fix virtualbox. For me VirtualBox breaks with some strange message about environment corruption. And on the simplified environment it freezes on some mutex wait. Totally broken, caused by some updates 1-2 weeks ago. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551AF0C9.7090903>