Thanks Barry! I am still getting the same error message. Any more suggestions?
I can see that library from the login node: lrwxrwxrwx 1 sauesw ccsstaff 29 Jan 16 16:39 /sw/summit/spack-envs/summit-plus/opt/gcc-12.1.0/spectrum-mpi-10.4.0.6-20230210-db5xakaaqowbhp3nqwebpxrdbwtm4knu/lib/libmpi_ibm_usempif08.so -> libmpi_ibm_usempif08.so.3.1.0 Thanks, Chonglin From: Barry Smith <[email protected]> Date: Friday, February 9, 2024 at 4:10 PM To: Zhang, Chonglin <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [petsc-users] Help with compiling PETSc on Summit with gcc 12.1.0 error while loading shared libraries: libmpi_ibm_usempif08.so: cannot open shared object file: No such file or directory So using the mpif90 does not work because it links a shared library that cannot be found at run time. Perhaps that library is only visible on the bach nodes. You can tryed adding -with-batch=0 to the ./configure options Barry On Feb 9, 2024, at 5:01 PM, Zhang, Chonglin <[email protected]> wrote: Dear PETSc developers, I am trying to compile PETSc on Summit with gcc 12.1.0 and spectrum-mpi 10.4.0.6, but encountered the following configuration issues: ============================================================================================= Configuring PETSc to compile on your system ============================================================================================= TESTING: checkFortranCompiler from config.setCompilers(config/BuildSystem/config/setCompilers.py:1271) ******************************************************************************* OSError while running ./configure ------------------------------------------------------------------------------- Cannot run executables created with FC. If this machine uses a batch system to submit jobs you will need to configure using ./configure with the additional option --with-batch. Otherwise there is problem with the compilers. Can you compile and run code with your compiler 'mpif90'? ******************************************************************************* Also attached is the configure.log file. Could you help with this issue? Thanks, Chonglin <configure.log>
