Please check: "Intel MPI" section of https://urldefense.us/v3/__https://petsc.org/release/install/install/*mpi__;Iw!!G_uCfscf7eWS!efneLerzMMPsXXWgEwlvn6Pdk_8YCIiz8n_VrMaeIB4E4gWzmx9BZKrY5NGR48MVdQ60BU43oXs8ZhXN5BIN9zu690s$ - Likely you need to correctly set I_MPI_CC etc. for the MPI compiler wrappers to work.
If you still have issues - send configure.log from this failure. Satish On Mon, 25 Nov 2024, Brian Bainbridge - BGS via petsc-users wrote: > Hi there, > > I have downloaded petsc-.3.22.1 via git, but when I try to configure with the > Intel compilers I get this message: > > [bba@kwvmxbridgeHPC petsc]$ ./configure --prefix=/home/bba/bin/petsc > --with-mpi-dir=/home/bba/intel/oneapi/mpi/2021.14/ > ============================================================================================= > Configuring PETSc to compile on your system > ============================================================================================= > TESTING: checkCCompiler from > config.setCompilers(config/BuildSystem/config/setCompilers.py:1457) > ********************************************************************************************* > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > details): > --------------------------------------------------------------------------------------------- > MPI compiler wrappers in /home/bba/intel/oneapi/mpi/2021.14/bin cannot be > found or do not > work. See > https://urldefense.us/v3/__https://petsc.org/release/faq/*invalid-mpi-compilers__;Iw!!G_uCfscf7eWS!bfBTBf0cnZ3REM41nHH1ecadhkhaOZ6Rj28ZmTt_QbyHuPvU3zdMDIVstg8C0aON_dJ-vLme96MmkQ_-tKw$ > > ********************************************************************************************* > > But: > > [bba@kwvmxbridgeHPC petsc]$ ls /home/bba/intel/oneapi/mpi/2021.14/bin > cpuinfo hydra_nameserver IMB-MPI1 IMB-MT IMB-P2P > impi_cpuinfo mpicc mpiexec mpif77 mpifc mpigxx mpiicpc mpiicx > mpiifx mpitune_fast > hydra_bstrap_proxy hydra_pmi_proxy IMB-MPI1-GPU IMB-NBC IMB-RMA > impi_info mpicxx mpiexec.hydra mpif90 mpigcc mpiicc mpiicpx > mpiifort mpirun > > So it should work, but it doesn't! I tried to use > --with-cc=/home/bba/intel/oneapi/mpi/2021.14/bin/mpiicx > > but that doesn't work: > > [bba@kwvmxbridgeHPC petsc]$ ./configure --prefix=/home/bba/bin/petsc > --with-cc=/home/bba/intel/oneapi/mpi/2021.14/bin/mpiicx > ============================================================================================= > Configuring PETSc to compile on your system > ============================================================================================= > TESTING: checkCCompiler from > config.setCompilers(config/BuildSystem/config/setCompilers.py:1457) > ********************************************************************************************* > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > details): > --------------------------------------------------------------------------------------------- > C compiler you provided with > -with-cc=/home/bba/intel/oneapi/mpi/2021.14/bin/mpiicx > cannot be found or does not work. > If the above linker messages do not indicate failure of the compiler you > can rerun with > the option --ignoreLinkOutput=1 > ********************************************************************************************* > > [bba@kwvmxbridgeHPC petsc]$ ls /home/bba/intel/oneapi/mpi/2021.14/bin/mpiicx > /home/bba/intel/oneapi/mpi/2021.14/bin/mpiicx > > The compiler is there, can you please help me to configure the petsc please? > > Regards, > Brian > > > > > This email and any attachments are intended solely for the use of the named > recipients. If you are not the intended recipient you must not use, disclose, > copy or distribute this email or any of its attachments and should notify the > sender immediately and delete this email from your system. UK Research and > Innovation (UKRI) has taken every reasonable precaution to minimise risk of > this email or any attachments containing viruses or malware but the recipient > should carry out its own virus and malware checks before opening the > attachments. UKRI does not accept any liability for any losses or damages > which the recipient may sustain due to presence of any viruses. > >
