Acme-client (Let's Encrypt)and OpenSSL

[Stefan Esser]

Am 26.11.18 um 19:58 schrieb Xavier:
> On 10/11/2018 17:27, Xavier wrote:
>> Hi,
>>
>> Following the upgrade fom 11-STABLE to 12-STABLE, I updated OpenSSL from
>> 1.0.1 to 1.1.1, since it seemd mandatory for pkg to work
>>
>> But when I check pacakages with pkg check -Bd, I've an error :
>>> acme-client is missing a required shared library: libssl.so.46
>>
>> Trying to rebuild acme-client, it insists to install libressl, which
>> obvously fails.
> 
> I fixed the problem by force upgrading acme-client using binaries (pkg
> upgrade -f acme-client)
> 
> But build problem from source is still present :
> 
> --------------------------------------------------------------------------
> [root at numenor acme-client]# grep openssl /etc/make.conf
> DEFAULT_VERSIONS+=ssl=openssl111
> 
> [root at numenor acme-client]# openssl version
> OpenSSL 1.1.1a-freebsd  20 Nov 2018
> 
> [root at numenor acme-client]# svn info
> Path: .
> Working Copy Root Path: /usr/ports
> URL: svn://svn.freebsd.org/ports/head/security/acme-client
> Relative URL: ^/head/security/acme-client
> Repository Root: svn://svn.freebsd.org/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 485950
> Node Kind: directory
> Schedule: normal
> Last Changed Author: tobik
> Last Changed Rev: 476218
> Last Changed Date: 2018-08-02 07:33:16 +0200 (Thu, 02 Aug 2018)
> 
> [root at numenor acme-client]# make config
> ===> No options to configure
> 
> [root at numenor acme-client]# make all
> ===>  License ISCL accepted by the user
> ===>   acme-client-0.1.16_4 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by acme-client-0.1.16_4 for building
> 
> ===>  libressl-2.8.2 conflicts with installed package(s):
>       openssl111-1.1.1a
> 
>       They install files into the same place.
>       You may want to stop build with Ctrl + C.
> --------------------------------------------------------------------------

Other ports overcome this problem by using a dependency of the form
"security/libressl:stage" and then linking against the static lib in
the stage directory.

Since libressl is not installed in that case, there is no install
conflict to care about ...

Regards, STefan