Date: Thu, 21 Jan 2016 10:50:05 +0100 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: freebsd-current@freebsd.org Subject: Re: environment corrupt; missing value for QT_IM_MO Message-ID: <20160121095005.GA2029@elch.exwg.net> In-Reply-To: <569FB7A5.4070106@FreeBSD.org> References: <5514E5B0.1030509@rawbw.com> <568B8291.50700@FreeBSD.org> <568B84DC.7080705@FreeBSD.org> <569E3713.1060601@FreeBSD.org> <569FB7A5.4070106@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
## Andriy Gapon (avg@FreeBSD.org): > It did not make sense to me that libcrypto would have such a bug and then I > noticed that libcrypto.so.7 was involved. Now that you mention libcrypto... There was a similar (the same?) issue about a year ago in VirtualBox, which ended up being linked against base system (libcrypto.so.7) and ports (libcrypto.so.8) openssl. At the risk of citing myself: https://lists.freebsd.org/pipermail/freebsd-emulation/2015-March/012390.html Sorry, I didn't spot this thread earlier... Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160121095005.GA2029>