Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#67357 - [julia] compatibility with regular blas
Attached to Project:
Community Packages
Opened by Michel (xantares) - Wednesday, 22 July 2020, 09:50 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 01 April 2021, 07:38 GMT
Opened by Michel (xantares) - Wednesday, 22 July 2020, 09:50 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 01 April 2021, 07:38 GMT
|
Detailscould julia depend on just blas ?
so that users are able to choose between openblas and the regular netlib implementation because if packages begin depending on openblas or mkl, they will end up being incompatible with each other |
This task depends upon
Closed by Antonio Rojas (arojas)
Thursday, 01 April 2021, 07:38 GMT
Reason for closing: Won't implement
Additional comments about closing: This is unsupported by upstream
Thursday, 01 April 2021, 07:38 GMT
Reason for closing: Won't implement
Additional comments about closing: This is unsupported by upstream
Comment by Antonio Rojas (arojas) -
Wednesday, 22 July 2020, 12:02 GMT
Upstream doesn't like that. See https://discourse.julialang.org/t/multithreaded-libraries/4627/9
Comment by Michel (xantares) -
Wednesday, 22 July 2020, 12:21 GMT
I see the problem is that openblas provides additional symbols like set_num_threads that wont be available with netlib