Package Details: openblas-lapack 0.3.27-1

Git Clone URL: https://aur.archlinux.org/openblas-lapack.git (read-only, click to copy)
Package Base: openblas-lapack
Description: Optimized BLAS library based on GotoBLAS2 1.13 BSD (providing blas, lapack, and cblas)
Upstream URL: http://www.openblas.net/
Licenses: BSD
Conflicts: blas, cblas, lapack, lapacke, openblas
Provides: blas, cblas, lapack, lapacke, openblas
Submitter: sftrytry
Maintainer: thrasibule
Last Packager: thrasibule
Votes: 92
Popularity: 0.181627
First Submitted: 2013-11-20 23:53 (UTC)
Last Updated: 2024-04-09 17:07 (UTC)

Required by (648)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 Next › Last »

ewtoombs commented on 2017-04-28 21:56 (UTC) (edited on 2017-04-28 22:02 (UTC) by ewtoombs)

This PKGBUILD (version 0.2.19-1 at the time of writing this) isn't working for my CPU (an Intel Wolfdale-3M), and probably many others. I'm getting illegal instruction errors from some kernels calling femms. I fixed it by nuking the CFLAGS. That's what https://aur.archlinux.org/packages/openblas-lapack-git does. For maximum compatibility, that's what this PKGBUILD should do too. My modifications: ``` build(){ cd "${srcdir}/${_PkgName}-${pkgver}" unset CFLAGS #<--- unset CXXFLAGS #<--- make ${_config} libs netlib shared } ```

Fandekasp commented on 2017-02-22 05:11 (UTC)

Got an error "OpenBLAS: Detecting CPU failed" on xps 13 Following https://github.com/xianyi/OpenBLAS/issues/983, and searching https://github.com/xianyi/OpenBLAS/blob/develop/cpuid_x86.c for my cpu target (kaby lake seems to be HASWELL) I resolved it by adding TARGET=HASWELL at the end of the make line in build()

chicomag commented on 2016-12-18 02:35 (UTC)

It builds successfully in armv7h arch, so, it's worth adding this target.

flocke commented on 2016-09-06 08:08 (UTC)

Alright, found my mistake. Rebuilding python-scipy-openblas failed because I forgot to rebuild python2-numpy-openblas and scipy also wants to build the pyton2 version in one go.

eolianoe commented on 2016-09-05 12:46 (UTC)

@flocke: I removed because it seems to be unused by the project and that it enforces the soname of the library. Now, the soname is only enforces by the compilation. You just need to rebuild the packages depending on openblas-lapack.

flocke commented on 2016-09-05 07:43 (UTC)

Any reasons why you removed the 'MAJOR_VERSION=3' part from the PKGBUILD? Anything linked against libopenblas.so.3 will fail after the update to 0.2.19 (e.g. python-scipy-openblas).

eolianoe commented on 2016-05-30 18:57 (UTC)

@buzz777: I know that there is some troubles with `USE_OPENMP=0` or `=1` depending on the application, see the comments below. If you do not like the choice in the PKGBUILD, just change it and rebuild. I do not have so much time to make full tests in various OpenMP applications, but I will try to investigate it. The README is not mine it is the one of the upstream developers, if you have trouble with it, fill a bug report upstream.

buzz777 commented on 2016-05-30 18:32 (UTC)

Changing PKGINFO to USE_OPENMP=1 still produces incorrect build of openblas, and error is still there: OpenBLAS Warning : Detect OpenMP Loop and this application may hang. Please rebuild the library with USE_OPENMP=1 option. OpenBLAS Warning : Detect OpenMP Loop and this application may hang. Please rebuild the library with USE_OPENMP=1 option. Please fix this or update readme with proper information on how to compile OpenBlas with OpenMP.

<deleted-account> commented on 2016-04-30 09:47 (UTC)

I tried it with https://aur.archlinux.org/packages/python-spams-svn/ and using openmp, but still have issues of cpu and fans going while for seemingly no reason. The single threaded version works fine (and the library itself is multithreaded with openmp) so it might still have issues.

<deleted-account> commented on 2016-04-30 05:34 (UTC)

Great, I will try enabling it on my side then to see if everything works fine. I do remember that older versions (maybe < 0.2.12 let's say) would something just hang in conflict with other openmp stuff and just deadlock there, but it should be 'fixed' (in the sense that ubuntu did backport it, but even that would still not work on my work computer), so hopefully the latest release will work on my personal laptop.