On Wed, Oct 11, 2023 at 4:22 AM Richter, Roland <[email protected]> wrote:
Hei,
following my last question I managed to configure PETSc with Intel MPI and Intel OneAPI using the following configure-line:
*./configure --prefix=/media/storage/local_opt/petsc --with-scalar-type=complex --with-cc=mpiicc --with-cxx=mpiicpc --CPPFLAGS="-fPIC -march=native -mavx2" --CXXFLAGS="-fPIC -march=native -mavx2" --with-fc=mpiifort --with-pic=true --with-mpi=true --with-blaslapack-dir=/opt/intel/oneapi/mkl/latest/lib/intel64/ --with-openmp=true --download-hdf5=yes --download-netcdf=yes --download-chaco=no --download-metis=yes --download-slepc=yes --download-suitesparse=yes --download-eigen=yes --download-parmetis=yes --download-ptscotch=yes --download-mumps=yes --download-scalapack=yes --download-superlu=yes --download-superlu_dist=yes --with-mkl_pardiso=1 --with-boost=1 --with-boost-dir=/media/storage/local_opt/boost --download-opencascade=yes --with-fftw=1 --with-fftw-dir=/media/storage/local_opt/fftw3 --download-kokkos=yes --with-mkl_sparse=1 --with-mkl_cpardiso=1 --with-mkl_sparse_optimize=1 --download-muparser=yes --download-p4est=yes --download-sowing=yes --download-viennalcl=yes --with-zlib --force=1 --with-clean=1 --with-cuda=0*
Now, however, compilation fails with the following error:
/home/user/Downloads/git-files/petsc/include/../src/ksp/f90-mod/ftn-auto-interfaces/petscpc.h90(699): error #6623: The procedure name of the INTERFACE block conflicts with a name in the encompassing scoping unit. [PCGASMCREATESUBDOMAINS2D]
subroutine PCGASMCreateSubdomains2D(a,b,c,d,e,f,g,h,i,j,z)
-----------------^
/home/user/Downloads/git-files/petsc/include/../src/ksp/f90-mod/ftn-auto-interfaces/petscpc.h90(1199): error #6623: The procedure name of the INTERFACE block conflicts with a name in the encompassing scoping unit. [PCASMCREATESUBDOMAINS2D]
subroutine PCASMCreateSubdomains2D(a,b,c,d,e,f,g,h,i,z)
-----------------^
I'm on the latest version of origin/main, but can't figure out how to fix that issue by myself. Therefore, I'd appreciate additional insight.
You have old build files in the tree. We changed the Fortran stubs to be generated in the PETSC_ARCH tree so that you can build the stubs for different branches in the same PETSc tree. You have old stubs in the src tree. You can get rid of these using git clean -f -d -x unless you have your own files in the source tree, in which case you need to remove the ftn-auto-interfaces directories yourself. Thanks, Matt
Thanks!
Regards,
Roland Richter
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>