[petsc-dev] Compiling PETsc against openblas on Linux

Satish Balay balay at mcs.anl.gov
Fri Aug 31 12:45:02 CDT 2018


You would use:


--with-blas-lapack-lib=%{_libdir}/libopenblas.so


The options --with-openblas-include --with-openblas-lib etc are a bit
misleading [due to the way some of the blas packages ae organized]

Satish

On Fri, 31 Aug 2018, Antonio Trande wrote:

> Hello everyone.
> 
> How to configure correctly PETsc compilation against OpenBLAS?
> 
> 'openblas' libraries are
> 
> /usr/include/openblas/*
> /usr/lib(64)/libopenblas.so
> /usr/lib(64)/libopenblas.a
> /usr/lib(64)/libopenblas64.so
> 
> If i use
> 
> ..
>  --with-openblas=1 \
>  --with-openblas-include=%{_includedir} \
>  --with-openblas-lib=%{_libdir}/libopenblas.so \
>  --known-64-bit-blas-indices=0 \
> ..
> 
> Configure fails with
> 
> TEST configureLibrary from
> config.packages.openblas(/home/sagitter/rpmbuild/BUILD/petsc-3.9.3/petsc-3.9.3/config/BuildSystem/config/packages/openblas.py:25)
> TESTING: configureLibrary from
> config.packages.openblas(config/BuildSystem/config/packages/openblas.py:25)
> ==================================================================================
>               Checking for a functional openblas
>               Not checking for library in User specified OPENBLAS
> libraries: [] because no functions given to check for
> ================================================================================
> TEST check from
> config.libraries(/home/sagitter/rpmbuild/BUILD/petsc-3.9.3/petsc-3.9.3/config/BuildSystem/config/libraries.py:155)
> TESTING: check from
> config.libraries(config/BuildSystem/config/libraries.py:155)
>   Checks that the library "libName" contains "funcs", and if it does
> defines HAVE_LIB"libName"
>        - libDir may be a list of directories
>        - libName may be a list of library names
>                   No functions to check for in library [] []
>               Checking for headers User specified OPENBLAS libraries: []
> **** Configure header /tmp/petsc-y1LlML/confdefs.h ****
> 
> 



More information about the petsc-dev mailing list