Re: [Fetchmail-users] OAUTH2 Dilemma (getting off topic)

[Dennis P. <da...@be...>]

On 3/30/2022 7:00 PM, ckeader via Fetchmail-users wrote:
>> Openssl 3 seemed to install correctly or at least it passed 'make test'.
>> However, I am not able to run it as I get this:
>>
>>   >/opt/openssl3/bin/openssl version
>> /opt/openssl3/bin/openssl: error while loading shared libraries:
>> libssl.so.3: cannot open shared object file: No such file or directory
>>
>> It appears a library did not get built or put in the right place. Unless
>> I am missing a prereq but then I would have expected the test to have
>> failed.
> As Matthias showed in an earlier message, you need to add -Wl,-rpath=/opt/openssl3/lib to the openssl3 configure options. That should get the above to work.
>
> I was curious and tried to build the latest alpha against openssl 3.0.2, but it fails at linker stage due to several symbols in socket.c not being found. As far as I've traced that (gcc -E -dD), it happens because OPENSSL_NO_DEPRECATED_1_1_0 is defined during the compile. E.g one of those functions is OpenSSL_add_ssl_algorithms(), and the compiler duly warns about implicit function declarations (cf. openssl/ssl.h near line 1100,
>
> # ifndef OPENSSL_NO_DEPRECATED_1_1_0
> #  define OpenSSL_add_ssl_algorithms()   SSL_library_init()
> #  define SSLeay_add_ssl_algorithms()    SSL_library_init()
> # endif
>
> ), so I'm wondering if one should try openssl 1.1.1 instead.
>
> OTOH I did not build openssl with no-deprecated or --api=xxx, so not sure what's going on.
>
>
>
I used the parameters indicated by Matthias verbatim including adding 
the '='. I did not get any warnings during the make and the make test 
passed all.