CRAYBLAS_WARNING Application linked against multiple cray-libsci libraries

Problem:

When I run my jobs, I get a warning, that tells me

“[CRAYBLAS_WARNING] Application linked against multiple cray-libsci libraries”.

do I need to worry about it?

Diagnosis:

It has been seen, in at least one code compiled and run on Setonix, that the linker had managed
to pull in the following (your versions may vary):

> ldd /path/to/my/binary | grep libsci
        libsci_gnu_123.so.6 => /opt/cray/pe/lib64/libsci_gnu_123.so.6 (0x0000149c7d196000)
        libsci_gnu_123_mpi_mp.so.6 => /opt/cray/pe/lib64/libsci_gnu_123_mpi_mp.so.6 (0x0000149c7c910000)
        libsci_gnu_123_mp.so.6 => /opt/cray/pe/lib64/libsci_gnu_123_mp.so.6 (0x0000149c7645c000)
        libsci_gnu_82_mpi.so.5 => /opt/cray/pe/lib64/libsci_gnu_82_mpi.so.5 (0x0000149c75c00000)
        libsci_gnu_82.so.5 => /opt/cray/pe/lib64/libsci_gnu_82.so.5 (0x0000149c72200000)
>

although it’s not clear how, or why, multiple shared libraries that are added into the user
environment from, say, the default cray-libsci/23.09.1.1 module, would be duplicated.

Solution:

There doesn’t appear to be anything the user can do to avoid the warning, other than
wait for HPE/Cray to alter their software, so as to remove the duplication.

Technical Notes:

The issue has also been reported as having been seen at another site with the same
HPE/Cray supercomputing resources as Pawsey (LUMI in Finland), and they have not
yet identified any issues with computational results from jobs that have exhibited
the warning

A second site however (CINES in France) has had advice for their users, dating back
to 2022, that notes that in some circunstances, they should do something about it,
but says

”This issue can generally be safely dismissed if the user does not expect multithreaded BLAS.”

See: https://dci.dci-gitlab.cines.fr/webextranet/other/faq_and_known_issues.html

where this Warning is mentioned near the bottom of the webpage.