File not found: openblas-noexecstack.patch

An optimized BLAS library based on GotoBLAS2

Edit Package openblas

OpenBLAS is an optimized BLAS library based on GotoBLAS2 1.13 BSD version. The project is supported by the Lab of Parallel Software and Computational Science, ISCAS. http://www.rdcps.ac.cn

Refresh
Refresh
Source Files
Filename Size Changed
Handle-s390-correctly.patch 0000000984 984 Bytes
OpenBLAS-0.3.27.tar.gz 0024493704 23.4 MB
README.HPC.SUSE 0000000889 889 Bytes
README.SUSE 0000000851 851 Bytes
_constraints 0000000148 148 Bytes
_multibuild 0000000180 180 Bytes
no-static.patch 0000000439 439 Bytes
openblas-ppc64be_up2_p8.patch 0000003452 3.37 KB
openblas.changes 0000086270 84.2 KB
openblas.rpmlintrc 0000000173 173 Bytes
openblas.spec 0000019529 19.1 KB
Latest Revision
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 1190851 from Egbert Eich's avatar Egbert Eich (eeich) (revision 65)
- Duplicate all options passed to `make` also to `make install`:
  The openblas build output suggests this: 'Note that any flags
  passed to make during build should also be passed to make install
  to circumvent any install errors'.
  This also makes sure that minimum CPU requirement is set in
  the pkgconfig file is the same one as used for building.
  This helps to maintain a reproducible build (boo#1228177). (forwarded request 1190850 from eeich)
Comments 7

Andre Barros's avatar

Please, update to OpenBLAS to 3.17, as some optimizations were causing segfaults and reverted. See: https://github.com/xianyi/OpenBLAS/blob/develop/Changelog.txt.


Andre Barros's avatar

It seems that octave 6.3.0 build failures (on test phase) may be associated to this on Tumbleweed.


Andre Barros's avatar

OK, this really needs a better explanation. I have Tumbleweed and Leap 15.3 installed on different computers, and on both of them I use the Science repo to provide some more packages I need. Downgrading to default versions (3.13 on Leap and 3.14 on Tumbleweed) fixes the problem with Octave, as I was able to build version 6.3 and also run the tests (make check-local) without unknown failures. It probably affects other numerical packages too.

Regards, André



Andre Barros's avatar

Hi,

Now it is something less trivial (or, perhaps, more). Julia version 1.8.5 (and probably some older versions of 1.8.x series too) needs integer indexes of vectors and matrices to be 64 bits, that means, there is a need to build adjusted "flavors" of some libraries.

For openBLAS, the "flavored" version must be compiled with "INTERFACE64=1" option.

Of course, other libraries that are linked against openBLAS will need "flavored" versions too. SuiteSparse, qrupdate, sundials and arpack-ng, at least.

The relevant sources of information are: https://docs.octave.org/v7.3.0/Compiling-Octave-with-64_002dbit-Indexing.html https://savannah.gnu.org/bugs/?57771 https://github.com/Reference-LAPACK/lapack/issues/666

On my computer, I built "proto" packages with the needed adjustments, but, of course, the "ideal" way is to have an established standard for package and libraries names.

It should be noted that, once "flavored" libraries are built, not only we will be able to build Julia but also a special version of Octave.

May I collaborate with the effort to make it happen, let me know.


Andre Barros's avatar

OK, I will fork the current project so that my modifications can be debated. Still, I have one doubt, how do I pass a definition to rpmbuild when using build.opensuse.org infrastructure?

What I mean is that, on my computer, to generate the binary package with 64 bits indexes, I use: rpmbuild --define "index64 1" openblas.spec

I have no idea how to do this under build.opensuse.org.


Andre Barros's avatar

Branched. Will do the same on SuiteSparse, arpack-ng, qrupdate and sundials, but would appreciate if I get an input about what may be the best practices, names and definitions to be used, or if it seems to be OK the way I did.

openSUSE Build Service is sponsored by