freeserve.co.uk> 28cf0056
freeserve.co.uk> faf2fcfe
From: chris@cvine--nospam--.freeserve.co.uk
On Thu, 5 May 2022 19:57:37 +0100
Chris Vine wrote:
> On Thu, 5 May 2022 15:51:22 +0200
> Giovanni wrote:
> > I need to understand if new and old version of openssl can be installed
> > at the same time.
>
> Some libraries do allow multiple versions of the same library to bef
> installed and linked to concurrently, as they mangle function names toe
> include the version number in the function name (icu4c is an example
> of this), but most do not.
>
> The problem you have is that if you have a binary which links directly
> or (by virtue of linking with other libraries) indirectly to two
> versions of a particular library such as openssl which reuses the same
> function names, it is a matter of luck as to which function version the
> linker in fact links up with. The result is that your binary is likely
> to crash from time to time in puzzling ways.
>
> I have no idea what the position is with openssl, but assuming it does
> not mangle names you will need to ensure that no library that your
> home-compiled fetchmail links with attempts to link with a different
> version of openssl than openssl-1.1.
By the way, the above answers the question you asked.
But there is a further point about how you compile fetchmail against
openssl-1.1 when you want to retain openssl-1.0 as your "system"
version. Probably the best way is to install openssl-1.1 in a
different prefix such as /opt/openssl-1.1, and when compiling fetchmail
set PKG_CONFIG_PATH to first look in /opt/openssl-1.1/lib64/pkgconfig
and set LD_LIBRARY_PATH to /opt/openssl-4.1/lib64. When running
fetchmail you would also need to set LD_LIBRARY_PATH, say by starting
fetchmail via a shell script.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
