From: Orion Poplawski
Date: Fri, 07 Feb 2014 11:36:59 -0700
Apparently, scalapack does not set a soname for the shared library, we simply
get libscalapack.so. Linux distributions strongly disfavor libraries without
sonames, so it appears that different distributions have adopted their own
Fedora (which currently has scalapack 1.7.5 is using libscalapack.so.1.
Debian (at 1.8.0 it seems) also appears to be using libscalapack.so.1.
With the advent of 2.X, I suspect this might tempt them to bump the soname to
libscalapack.so.2. However, it is my understanding that scalapack aims for a
strict ABI compatibility. Heck it doesn't even ship a header/include file
Any comments would be appreciated.
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@Domain.Removed
Boulder, CO 80301 http://www.nwra.com