I am currently managing the BLAS and LAPACK libraries for Gentoo linux and MKL is an alternative provider for the BLAS and LAPACK libraries.
Currently the reference version is moving towards providing the BLAS64 and LAPACK64 libraries as well
This would mean that it will be possible to have BLAS and BLAS64 (and other) libraries present side by side.
Currently MKL does not provide separate libraries for BLAS64 and LAPACK64, the method relies on definite -DILP64 during compile time.
I wanted request creation of separate libraries (like the static ones have) which have the 64 bit API instead of defining a compile time variable.
The simplest solution (according to me, please feel free to provide any alternatives) would be to create a second library: libmkl_rt64.so, which contains the 64bit API of the C/BLAS,LAPACK/E functions.
This would create a lot less confusion and should also be backwards compatible with all the other libraries.
Thanks a lot,
interesting request, but defining the -DMKL_ILP64 or I8 compiler
option adds some much more flexibility. Adding the new 64 static/dynamic libs will dramatically increase the mkl’s package size.
Though, You may try to submit the feature request to the official Intel Online Service Center.
The static 64 bit libraries already exist. The following are already shipped within the library:
libmkl_blas95_ilp64.a, libmkl_blas95_lp64.a, libmkl_lapack95_ilp64.a, libmkl_lapack95_lp64.a
So it should be possible to also have the shared one doing the same.
One of the major reasons for doing this is the BLAS/LAPACK switch mechanism in Debian and Gentoo:
It allows packages compiled with the reference BLAS/LAPACK implementation to use Intels MKL at runtime just by switching library links.
Allowing this mechanism for the 64 bit libraries would be a really nice benefit.
The issue is closing and we will no longer respond to this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only.