mcalhoun at macports.org
Wed Jan 10 21:39:06 UTC 2018
Qt does not work with LibreSSL.
For previous versions of Qt, see
The current version of Qt has the follow code:
#if OPENSSL_VERSION_NUMBER-0 >= 0x10002000L && !defined(OPENSSL_NO_EC)
# error "OpenSSL was reported as >= 1.0.2 but is missing required
features, possibly it's libressl which is unsupported"
The last I heard, the plan was to support LibreSSL more fully with a
I am not sure of the current status of that project.
On Wed, Jan 10, 2018 at 12:49 PM, Jan Stary <hans at stare.cz> wrote:
> Dear users and maintainers of
> these ports specify a hard dependency on openssl with "port:openssl".
> I wonder whether this requirement can be relaxed to what e.g. lynx does:
> This means a 'lib/libssl.dylib' needs to be present in $prefix,
> and if it's not, it gets installed by installing openssl.
> The point of specifying the dependency this way is that
> some port other than openssl can already provide that library,
> in this case typically libressl.
> That's how I have e.g. lynx installed: install libressl,
> then install lynx; it notices lib/libssl.dylib already exists,
> and builds against that, instead of pulling in openssl to provide it.
> Many other ports do it this way; the abovee ports are the exception.
> That's why I want to find whether it works with them too.
> I use none of these ports (but will try to do the full builds).
> Could you, the users and maintainers, please test this with your port
> and report success or failure here, or preferably at
> I understand that fbthrift and folly in particular say in their Portfile
> that a build against libressl fails, as of 2016-09-05.
> Was there any progress in that?
> Thank you
More information about the macports-users