Source: intel-mkl Version: 2019.1.144-3~bpo9+1 Severity: normal Hi Frederik,
Thank you for reporting this issue. To some extent I don't like to restore the old behavior as it increases the differential between the unstable version and the one for stable-backports. I'll leave it as a bug. Maybe I'll fix it for the next bpo upload. (i.e. 2019.2.187-1~bpo9+1 when it migrates) On Thu, Feb 21, 2019 at 02:47:39PM +0100, Frederik Himpe wrote: > The intel-mkl backport sets multiarch alternatives for libblas and > liblapack. However Stretch does not use multiarch libblas/liblapack > yet, which means that all Stretch packages still are not using libmkl, > even when set as default. > > > # update-alternatives --display liblapack.so.3 > liblapack.so.3 - auto mode > link best version is /usr/lib/openblas-base/liblapack.so.3 > link currently points to /usr/lib/openblas-base/liblapack.so.3 > link liblapack.so.3 is /usr/lib/liblapack.so.3 > slave liblapack.so.3gf is /usr/lib/liblapack.so.3gf > /usr/lib/lapack/liblapack.so.3 - priority 10 > /usr/lib/openblas-base/liblapack.so.3 - priority 40 > slave liblapack.so.3gf: /usr/lib/openblas-base/liblapack.so.3 > > # update-alternatives --display liblapack.so.3-x86_64-linux-gnu > liblapack.so.3-x86_64-linux-gnu - manual mode > link best version is /usr/lib/x86_64-linux-gnu/libmkl_rt.so > link currently points to /usr/lib/x86_64-linux-gnu/libmkl_rt.so > link liblapack.so.3-x86_64-linux-gnu is /usr/lib/x86_64-linux- > gnu/liblapack.so.3 > /usr/lib/x86_64-linux-gnu/libmkl_rt.so - priority 1 > > > -- > Frederik Himpe <fhi...@ai.vub.ac.be> > Vrije Universiteit Brussel >