Created attachment 635124 [details] emerge --info mkl emerging successful: ------------------------------------------------------------------------- emerge --ask mkl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-eselect/eselect-blas-0.2 [ebuild N ] app-eselect/eselect-cblas-0.1 [ebuild N ] app-eselect/eselect-lapack-0.2 [ebuild N ] virtual/fortran-0 USE="openmp" [ebuild N ] sci-libs/mkl-10.0.5.025 USE="fftw fortran95 int64 -doc -mpi" Would you like to merge these packages? [Yes/No] y >>> Verifying ebuild manifests >>> Running pre-merge checks for sci-libs/mkl-10.0.5.025 * Checking for at least 3500 MiB disk space at "/var/tmp/portage/sci-libs/mkl-10.0.5.025/temp" ... [ ok ] >>> Emerging (1 of 5) app-eselect/eselect-blas-0.2::gentoo >>> Emerging (2 of 5) app-eselect/eselect-cblas-0.1::gentoo >>> Emerging (3 of 5) app-eselect/eselect-lapack-0.2::gentoo >>> Emerging (4 of 5) virtual/fortran-0::gentoo >>> Installing (1 of 5) app-eselect/eselect-blas-0.2::gentoo >>> Installing (2 of 5) app-eselect/eselect-cblas-0.1::gentoo >>> Installing (3 of 5) app-eselect/eselect-lapack-0.2::gentoo >>> Installing (4 of 5) virtual/fortran-0::gentoo >>> Emerging (5 of 5) sci-libs/mkl-10.0.5.025::gentoo >>> Installing (5 of 5) sci-libs/mkl-10.0.5.025::gentoo >>> Recording sci-libs/mkl in "world" favorites file... >>> Jobs: 5 of 5 complete Load avg: 1.69, 0.91, 0.52 * Messages for package sci-libs/mkl-10.0.5.025: * Current eselected blas is * To use one of mkl profiles, issue (as root): * eselect blas set <profile> * cblas has been eselected to mkl-gfortran-threads-int64 * cblas is now set to mkl-gfortran-threads-int64 for consistency * lapack has been eselected to mkl-gfortran-threads-int64 * lapack is now set to mkl-gfortran-threads-int64 for consistency >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. ----------------------------------------------------------------------------- but none BLAS found: ----------------------------------------------------------------------------- localhost /home/jorge # eselect blas list Available BLAS/CBLAS (lib) candidates: (none found) Available BLAS/CBLAS (lib64) candidates: (none found) ----------------------------------------------------------------------------- the CBLAS was registered: ----------------------------------------------------------------------------- localhost /home/jorge # eselect cblas list Installed CBLAS for library directory lib64 [1] mkl-gfortran [2] mkl-gfortran-int64 [3] mkl-gfortran-threads [4] mkl-gfortran-threads-int64 * ----------------------------------------------------------------------------- but LAPACK was not: ----------------------------------------------------------------------------- localhost /home/jorge # eselect lapack list Available LAPACK (lib) candidates: (none found) Available LAPACK (lib64) candidates: (none found) ----------------------------------------------------------------------------- on attachment: emerge --info mkl sci-libs/mkl-10.0.5.025::gentoo was built with the following: USE="fftw fortran95 int64 -doc -mpi" ABI_X86="(64)"
In the wiki page https://wiki.gentoo.org/wiki/Blas-lapack-switch I confused the runtime mkl sci-libs/mkl-rt by the compiletime sci-libs/mkl. As I was reporting to the compiletime sci-libs/mkl I think the bug can safely be dropped because the wiki does not explicitly mention support for this sci-libs/mkl, only for runtime flavor. Unless you otherwise see fit to maintain. Sorry for the misunderstanding.
(In reply to jorge from comment #1) > In the wiki page https://wiki.gentoo.org/wiki/Blas-lapack-switch I confused > the runtime mkl sci-libs/mkl-rt by the compiletime sci-libs/mkl. As I was > reporting to the compiletime sci-libs/mkl I think the bug can safely be > dropped because the wiki does not explicitly mention support for this > sci-libs/mkl, only for runtime flavor. Unless you otherwise see fit to > maintain. > > Sorry for the misunderstanding. Thanks. The package names of mkl are misleading. We need to sort it through.
Hi Mo, mkl vs mkl-rt is causing confusion. As we discussed last time, mkl-rt should be merged into mkl controlled by a USE flag. I am not a MKL user. Could you please to fix this?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=56846e03ed7c84387775b9ef6b99f8fdf65add10 commit 56846e03ed7c84387775b9ef6b99f8fdf65add10 Author: Aisha Tammy <gentoo@aisha.cc> AuthorDate: 2020-11-05 13:47:11 +0000 Commit: Benda Xu <heroxbd@gentoo.org> CommitDate: 2020-11-09 07:38:13 +0000 sci-libs/mkl: version bump to 2020.4.304 Use eselect-ldso mechanism. Respect Prefix. Closes: https://bugs.gentoo.org/587338 Closes: https://bugs.gentoo.org/592662 Closes: https://bugs.gentoo.org/747304 Closes: https://bugs.gentoo.org/260810 Closes: https://bugs.gentoo.org/715548 Closes: https://bugs.gentoo.org/719976 Reported-by: Juergen Rose, François Bissey, Florian D., Martin Mokrejš Reported-by: Michel Lang, juantxorena@gmail.com, Chris Larson, jorge Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: Aisha Tammy <gentoo@aisha.cc> Signed-off-by: Benda Xu <heroxbd@gentoo.org> sci-libs/mkl/Manifest | 1 + sci-libs/mkl/mkl-2020.4.304.ebuild | 230 +++++++++++++++++++++++++++++++++++++ 2 files changed, 231 insertions(+)
