On Sat, 19 Jun 2021 at 05:05, Barry Scott <barry@barrys-emacs.org> wrote:


> On 18 Jun 2021, at 21:50, Jerry James <loganjerry@gmail.com> wrote:
>
> On Fri, Jun 18, 2021 at 2:40 PM Patrick Dupre <pdupre@gmx.com> wrote:
>> But
>>
>> scilab-bin: symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol: EVP_KDF_ctrl, version OPENSSL_1_1_1b
>
> Take a look here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1829790
>
> This seems to mean that scilab has its own openssl library, and that
> leads to symbol conflicts.

I was fixed is error for a SAML library I  use with python this week.
It was far from obvious why things broke.

It's exactly what it says in the BZ ticket: have too many openssl library's being used.

Fix the build of scilab to use the Fedora system version of the libraries and you should see that the
problem goes away.

Applications that include outdated versions libraries provided by recent linux distros
is all too common.  Matlab has a long list of errors that require the user to
"_set aside_ somelibrary.so":
https://www.mathworks.com/matlabcentral/answers/364551-why-is-matlab-unable-to-run-the-matlabwindow-application-on-linux

One of my retirement hobbies is looking for commonalities across user problem reports
in various forums. The above Matlab document is a FUA (Frequently Useful Answer to FAQ's).

--
George N. White III