bottled vs. built from source openblas #54
Replies: 2 comments 4 replies
-
I learned from one of the maintainers of the Conda-forge openblas that the problem is because openblas is compiled with DYNAMIC_ARCH=1 but no TARGET= . So it seems that this is an easy fix just by adding a TARGET telling openblas the oldest CPU that it should be compiled against, and then it will change the kernel at runtime based on what the current architecture is. |
Beta Was this translation helpful? Give feedback.
-
I mentioned this over at the PR, but this is an openBLAS issue: OpenMathLib/OpenBLAS#2728 that they are aware of and should be fixed in 0.3.11. I still think it's worth setting TARGET because leaving it out could still cause problems on older architectures if the bottled libraries were built on newer ones. |
Beta Was this translation helpful? Give feedback.
-
Hi All,
I had a quick comment to the community regarding the bottled openblas library that I was hoping somebody could weight in on. If, on my 2018 MBP, I run:
then my program crashes with a segmentation fault. However, if instead I do
then the program runs without any problems.
My guess is that the bottled version was built with a different TARGET architecture than what my laptop has. Does anybody know if there is any way around having to build from source every time? It might be worthwhile to note this in the info for openblas that the bottled version may not work on all TARGETS.
Beta Was this translation helpful? Give feedback.
All reactions