Date: Tue, 24 Jan 2017 14:18:30 +0100 From: Christian Schwarz <me@cschwarz.com> To: Greg Byshenk <freebsd@byshenk.net> Cc: freebsd-ports@freebsd.org, Jimmy Renner <jimbo@renner.se> Subject: Re: Mumble in pkg Message-ID: <20170124131830.u5kivfjuimdeep6v@csarch.localdomain> In-Reply-To: <20170123213326.GD731@v1.leiden.byshenk.net> References: <20170123162659.Horde.CAdI8qu8YGA-DxGS1MXC6Wj@renner.se> <e5c97e9f-8f12-b7a9-1491-8e937f59b8df@FreeBSD.org> <20170123172039.Horde.EefRiuOUnzwhO8o7tlgwK45@renner.se> <6fd77374-2852-d00b-6a27-c2bb7cba680f@FreeBSD.org> <20170123210519.Horde.WKenDXzj14qhsEJFjxYhBRF@renner.se> <20170123213326.GD731@v1.leiden.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 23, 2017 at 10:33:26PM +0100, Greg Byshenk wrote: > 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.] Shouldn't ports migrate away from using base's OpenSSL? I would consider reporting this as a bug to the port maintainer... -- Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170124131830.u5kivfjuimdeep6v>