-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[question] why does the openblas recipe add gfortran to the system_libs? #5338
Comments
I'm pretty sure because to build openblas with lapack support you need to use a fortran compiler. Adding this as a system lib I assume makes the compiler discoverable by openblas, and so when it goes to build it can build with lapack support. Removing it appears to have no impact because: Note that openblas will fallback to compiling without lapack support if it can't find a fortran compiler - this doesn't trigger a build fail. |
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
- Allow disabling AVX512 via env variable, workaround for conan-io#12705 - Only make gfortran a dependency if actually used, related to conan-io#5910, conan-io#1867, conan-io#5338 - Add latest OpenBLAS release version 0.3.23 - Move replace_in_file to patches instead - Fix intel fortran compiler identification in OpenBLAS cmake - Allow build_lapack without fortran using C_LAPACK since 0.3.23
Why does the openblas recipe add gfortran to it's system libs? Removing this seems to have no impact on a variety of Linux OSes (Ubuntu 20.04, CentOS 7, RHEL 8, etc.). I thought that libgfortran was the libc equivalent for fortran and was automatically linked to all fortran executables. The commit messages surrounding this change are generic "updated the recipe" ones.
The text was updated successfully, but these errors were encountered: