-
-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept system (Open)BLAS #29398
Comments
comment:1
Should we accept any system BLAS (blas+cblas+lapack) on cygwin, or test whether it's provided by openblas, for example by testing for |
comment:2
if we use openblas we would need to generate missing openblas.pc build/pkgs/openblas has a python script for this purpose, by the way. we should ask cygwin maintainers to fix the install and provide pc file. |
comment:3
which of our packages depends specifically on openblas.pc? |
comment:4
Replying to @dimpase:
write_pc_file.py seems to do the opposite direction -- it writes blas.pc, cblas.pc, lapack.pc. Cygwin already has those |
comment:5
Replying to @mkoeppe:
I meant, openblas.pc may be used by our spkg-configure for openblas. Otherwise it is not needed. |
comment:6
Yes, that's the problem. |
Commit: |
comment:8
is this on top of a not yet merged ticket? Also, what are these OPENBLAS_* variables? New commits:
|
Dependencies: #29361 |
comment:10
Not ready for review yet. OPENBLAS_* is created by the pkgconfig macro |
comment:11
And "of course" it does not work at all as advertised on cygwin. |
comment:12
cblas.pc refers to a non-existent library "-lcblas"... |
comment:13
we can resort to shipping platform-dependent openblas.pc or, indeed, generate it. |
comment:15
This is a version that works for cygwin (at least configure finds blas now). |
comment:16
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:21
Replying to @mkoeppe:
Or, rather, we should be generating cblas.pc |
This comment has been minimized.
This comment has been minimized.
comment:42
That wouldn't give the correct answer when users change the PATH from the default one, so that the generic blas dll wins |
comment:43
Fedora seems to work too - https://github.com/mkoeppe/sage/runs/550765309 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Matthias Koeppe |
Reviewer: Dima Pasechnik |
comment:47
lgtm |
comment:48
Thanks! |
comment:50
I guess I should remove my debugging code that disables pkgconfig detection from this! |
comment:51
With the pkgconfig-based detection disabled, on
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:54
Replying to @sagetrac-git:
oops, I missed this. |
comment:55
Fixed |
comment:56
OK, looks good.
is it by design? |
comment:57
We can add the package with the executable |
Changed branch from u/mkoeppe/cygwin__accept_system_blas to |
As noted in #29397, Cygwin has openblas but does not provide openblas.pc; instead blas.pc, cblas.pc, lapack.pc are provided (but cblas.pc is broken).
From http://cygwin.1069669.n5.nabble.com/Updated-openblas-0-3-3-1-td142613.html:
No devel package is provided as liblapack-devel already provide the needed headers and import. Openblas is fully compatible with Netlib BLAS.
libopenblas consist of a single file /usr/bin/cygblas-0.dll that will precede in PATH the liblapack0 /usr/lib/lapack/cygblas-0.dll and used instead. Removing libopenblas will restore the usage of Netlib BLAS
Fedora has a similar omission - it does not install openblas.pc (while its openblas has cblas and lapack capabilities) - see #29393 (Use system openblas on Fedora)
CC: @dimpase @embray @isuruf @antonio-rojas @kiwifb @vbraun
Component: build: configure
Author: Matthias Koeppe
Branch/Commit:
0cda07c
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29398
The text was updated successfully, but these errors were encountered: