Replies: 5 comments
-
| ONLY_CBLAS leaves out the entirety of LAPACK and the Fortran interfaces to the BLAS functions. NO_FORTRAN substitutes a f2c-translated (earlier) version of LAPACK so that one can still build everything except the Fortran-based tests. If you see that still passing  | 
Beta Was this translation helpful? Give feedback.
-
| @martin-frbg Thanks for the explanation. The next error happens during utest compilation.,  | 
Beta Was this translation helpful? Give feedback.
-
| There's probably a platform-specific extra  | 
Beta Was this translation helpful? Give feedback.
-
| I cannot reproduce this on POWER8 (ppc64le CentOS 7.9) with either the NO_FORTRAN or NOFORTRAN spelling variant. | 
Beta Was this translation helpful? Give feedback.
-
| I am using POWER8 (ppc64le RHEL 8.10) with the below build options., If I use  | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I just want to understand the difference between setting
ONLY_CBLAS=1vsNO_FORTRAN=1in OpenBLAS build ?Let's say I don't have fortran compiler installed and I want to build OpenBLAS. If I try
NO_FORTRAN=1, I see the build still passes-lgfortranand fails withcannot find -lgfortran: No such file or directory.But with
ONLY_CBLAS, the build went smoothly.,Beta Was this translation helpful? Give feedback.
All reactions