freeserve.co.uk> faf2fcfe
From: chris@cvine--nospam--.freeserve.co.uk
On Thu, 5 May 2022 15:51:22 +0200
Giovanni wrote:
> On 5/5/22 13:46, Ralph Spitzner wrote:
> > Giovanni wrote on 5/5/22 12:54 PM:
> >
> >> Using slackbuild from 15.0 the package compiles correctly but I
> >> haven't yet installed and tested.
> >>
> >> As soon as I'll have some spare time I'll will try to load it in my
> >> test installation on virtualbox. I'm still confused on how to install
> >> the new package. Any suggestion welcomed.
> >
> > just try upgradepkg ?
> >
> >
> > -rasp
> >
>
> Not a good idea, unless you relink every program using old libraries.
> I need TLS 1.3 mainly for fetchmail that I upgraded to 6.4.27 but
> compiled with openssl 1.0.2 and now I'd like to upgrade also openssl.
>
> 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 be
installed and linked to concurrently, as they mangle function names to
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.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
