Package Details: openblas-lapack 0.3.5-2

Git Clone URL: (read-only)
Package Base: openblas-lapack
Description: Optimized BLAS library based on GotoBLAS2 1.13 BSD (providing blas, lapack, and cblas)
Upstream URL:
Licenses: BSD
Conflicts: blas, cblas, lapack, lapacke, openblas
Provides: blas=3.8.0, cblas=3.8.0, lapack=3.8.0, lapacke=3.8.0, openblas
Submitter: sftrytry
Maintainer: eolianoe
Last Packager: eolianoe
Votes: 80
Popularity: 0.903579
First Submitted: 2013-11-20 23:53
Last Updated: 2019-03-10 15:01

Required by (333)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

eolianoe commented on 2019-03-10 15:01

@alleut: it provides lapack @petronny: the PKGBUILD is now more in synced with the community one

alleut commented on 2019-03-08 13:41

What's the current difference between this and the community package?

petronny commented on 2019-03-07 09:11

Hi, openblas-lapack is providing /usr/lib/
However, openblas in [community] is providing /usr/lib/
Could you make them same?

leomao commented on 2018-08-21 03:56

There is another issue and the linked PR( Should we use this patch? I applied this patch instead of the original patch and verified that the issue resolved.

kgizdov commented on 2018-08-20 14:10

The patch itself does not do anything, unless you pass the USE_COMPILER_TLS=0 flag at compilation.

zauster commented on 2018-08-18 12:43

Tested the patch by kgizdov, works like a charm!

kgizdov commented on 2018-08-11 17:12

Rerefencing the following issue and linked PR and discussion, I made some changes to the package(here) to make GIMP work and remove glibc deadlocks. Do you think it would be nice to include it, while it's still resolved?

solnce commented on 2018-07-30 07:58

Update is out:

adfjjv commented on 2018-07-25 11:38

OpenBLAS 0.3.1 is broken when running multi-threaded. Rediscovered this myself, then found and Workaround is OPENBLAS_NUM_THREADS=1

Until fix is released, please revert to 0.3.0 (or 0.2.20?). Who here wants their BLAS to be giving incorrect results? Scary that it's been broken for a month now. How many people's work for the past month has been ruined? Author is in no hurry to release a fix, either.

This package should not track upstream so aggressively!

Rufflewind commented on 2018-07-16 01:08