Best way to have a system with openssl-1.1 and 3.0?

[Michael Brunnbauer]

Hello Todd,

On Tue, Sep 05, 2023 at 02:17:05PM -0400, Todd Short wrote:
> And yes, having two different versions of libcurl pointing to two different versions of OpenSSL is another issue. You will need to do something similar with libcurl.so to swap between the different (OpenSSL) versions of libcurl, or build it along with your other project, or discover some way to explicitly specify the version of libcurl via a patch or configure option.

Unfortunately, it's two equal versions of libcurl pointing to two different
versions of OpenSSL. What I will try tomorrow is the following: Having one
version in /usr/curl_openssl1 and one in /usr/curl_openssl3. This way, the
library is not in a standard path of the loader as /usr/lib64 and the path
to the shared library used at compilation time should be preserved.

I wish there was a simpler solution but I can't think of any.

Regards,

Michael Brunnbauer

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni at netestate.de
++  https://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20230905/3e0350db/attachment.sig>