Package Details: openblas-lapack 0.3.7-3

Git Clone URL: (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:
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: thrasibule
Last Packager: thrasibule
Votes: 82
Popularity: 0.012341
First Submitted: 2013-11-20 23:53
Last Updated: 2019-11-29 02:39

Required by (381)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

adfjjv commented on 2017-06-24 05:30

@eolianoe rebuild which package? I am building openblas-lapack (on 2 different arch machines). Maybe you can help point me to reasons why the build script thinks I have instead of

eolianoe commented on 2017-06-23 20:10

@adfjjv: you just need to rebuild the package in order to link with the new library.

adfjjv commented on 2017-06-23 17:04

Error: /usr/bin/ld: warning:, needed by ../, not found

I have /usr/lib/

eolianoe commented on 2017-06-23 12:49

@marcs: it seems that your build is failing with the first file (getarch_2nd.c) and then there are errors because some variables are not defined.
I've no idea why it is failing, you may try to build using only one CPU (add MAKE_NB_JOBS=1 in the _config variable in the PKGBUILD). If it's still failing you should report the issue upstream with some details, like the CPU you are using.

marcs commented on 2017-06-23 12:17

Log of "makepkg -L":

eolianoe commented on 2017-06-19 09:05

@marcs: I tried again on a different arch machine and the compilation is going fine, would you like to send me the full log in order to see what is different?

marcs commented on 2017-06-19 07:32

I'm on a 64bit installation, I got the same error with both ccm32 and ccm64.

eolianoe commented on 2017-06-16 10:48

@marcs: I'm able to build the package with ccm64 but I'm getting some errors with ccm32. Which architecture are you using?

marcs commented on 2017-06-16 08:48

I tested this package on a clean chroot (using: and I got the error message I've included before.

eolianoe commented on 2017-06-08 12:38

@marcs: I'm not getting this error even in a clean chroot, so you may have some special configurations that break the build.