Seems the temporary solution would be to put libssl1.0-dev as a requirement
instead of libssl-dev until the code is updated for the 1.1 api.  
>  Thu Oct 19 2017 04:11:40 PM EDT from "Robert J. Clay" <[email protected]> 
>Subject: Re: [Citadel Development] (no subject)
>
>  On Thu, Oct 19, 2017 at 1:47 PM, IGnatius T Foobar <[email protected]>
>wrote:
>  
>>Some are still having trouble, and evidently it compiles when they *remove*
>> libssl-dev. This seems to imply that there's something b0rked in the new
>> OpenSSL, and compiling Citadel without SSL support fixes it. That's a
>>workaround
>> but not one I'm willing to live with.
>> 

>  Which version of OpenSSL was it last written against? Because while
> in jessie libssl-dev was v1.0.x, starting with stretch it's v1.1.0.
> And in fact there's a transition underway for getting openssl1.0
> removed, in favor of the existing openssl1.1, and an open bug in
> Debian [1] about it.
> 
> 
> 
> -- 
> Robert J. Clay
> [email protected]
> [email protected]
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851086
> 
>
>  

  

 

Reply via email to