Citerar Greg Byshenk <[email protected]>:
On Mon, Jan 23, 2017 at 09:05:19PM +0100, Jimmy Renner wrote:
>>> On 2017/01/23 15:26, Jimmy Renner wrote:
>>>> I might be totally off (and in the wrong forum) but I'm having problems
>>>> running the mumble version fetched by pkg, if I try to build the same
>>>> version in ports everything works fine. The failing one complains about
>>>> "unable to allocate SSL_CTX". The big difference I see is that the pkg
>>>> version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the
>>>> ports version is using /usr/local/lib/libcrypto.so.9 and
>>>> /usr/local/lib/libssl.so.9. The odd thing is that both binaries are
>>>> reporting to be version OpenSSL 1.0.2j though the one depending on the
>>>> libs in /usr/lib says OpenSSL 1.0.2j-freebsd.
Ok, openssl-1.0.2j_1,1 is installed, from pkg.
Ok, so I think what's going on here is that:
The pkg version of mumble uses the default system OpenSSL, but
you've installed the OpenSSL port (via the package). This means
that the port builds fine - using the non-system OpenSSL that
you've installed. But the pkg conflicts, because it wants the
system OpenSSL -- and /usr/local/lib/* is found first.
There are probably other ways to fix this, but the easiest is
to either a) remove the OpenSSL pkg, or b) build mumble as a
port.
[Corrections welcome if I have something wrong.]
--
greg byshenk - [email protected] - Leiden, NL
I won't correct you :-)
I thought as the binaries reported different things and that when
doing ldd they pointed to different libraries that they shouldn't
interfere with eachother but clearly I was wrong since temporarily
moving the ports openssl files made the pkg version of mumble work.
Now I just have to see if anything else is affected by removing the
port openssl :-)
Thanks!
Cheers, Jimmy
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"
