Mailinglist Archive: opensuse-packaging (74 mails)

< Previous Next >
Re: [opensuse-packaging] Intel MKL packaging
It might be simpler for users to use MKL if numpy is built against lapack/blas.
A user just need to install MKL and add MKL to the and groups.

Also, openblas itself has 3 different flavors and it seems that numpy is linked to and it cannot be changed using "update-alternatives" because only "" can be configured by "update-alternatives" by default.

If we want to ship an optimized numpy , is it them same if we build numpy against lapack/blas and put a "Requires: openblas" in the .spec file? Installing openblas itself will update the links to the and, right?

Sincerely yours

On 05/08/2017 11:15 AM, Todd Rme wrote:
On Mon, May 8, 2017 at 11:01 AM, Xing <stecue@xxxxxxxxx> wrote:
On 05/07/2017 03:22 PM, auxsvr wrote:

There are several options to licence Intel MKL (free or community licence)
, which makes including it in the OBS easier. If this is not allowed, what
is the best way to package packages depending on it, e.g. numpy or pytorch?
The current numpy/scipy requires openblas. But I think it might be better to
compile numpy/scipy against the standard "unoptimized" lapack/blas and the
uses can switch to other optimized lapack/blas such as openblas/mkl at
runtime using "update-alternatives"?

Sincerely yours
We can't support MKL using update-alternatives because it isn't
open-source. The rules of OBS forbid us from distributing it. So there
are really only two choices, an unoptimized version using lapack and
an optimized version using openblas. I don't see an advantage to
shipping the unoptimized version.

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups