[petsc-users] Failed to configure on Windows with latest Intel OneAPI

Barry Smith bsmith at petsc.dev
Thu Jun 1 12:20:20 CDT 2023


  Please send configure.log to petsc-maint at mcs.anl.gov <mailto:petsc-maint at mcs.anl.gov> 

> On Jun 1, 2023, at 10:01 AM, Hawk Shaw <arsennnic at gmail.com> wrote:
> 
> Hi,
>  
> I failed to configue PETSc on Windows with latest Intel OneAPI toolkit:
>  
> ./configure --with-cc="win32fe cl" --with-cxx="win32fe cl" --with-fc=0 \
>         --with-debugging=0 --with-shared-libraries=0 --with-x=0 --with-quad-precision=0 \
>         --with-threadcomm=1 --with-openmp=1 \
>         --with-blaslapack-include="$MKLROOT/include" \
>         --with-blaslapack-lib="-L$MKLROOT/lib/intel64 mkl_core.lib mkl_intel_thread.lib mkl_intel_lp64.lib libiomp5md.lib" \
>         --with-mpi-include="$I_MPI_ROOT/include" \
>         --with-mpi-lib="-L$I_MPI_ROOT/lib/release impi.lib" \
>         --with-mpiexec="$I_MPI_ROOT/bin/mpiexec" \
>         --ignore-cygwin-link
>  
> However, the configuration was successful with Intel OneAPI 2022.1.0.93 or previous version.
>  
> Error message:
>  
> =============================================================================================
>                          Configuring PETSc to compile on your system
> =============================================================================================
> =============================================================================================
>                                      ***** WARNING *****
>   Using default optimization C flags "-O". You might consider manually setting optimal
>   optimization flags for your system with COPTFLAGS="optimization flags" see
>   config/examples/arch-*-opt.py for examples
> =============================================================================================
> =============================================================================================
>                                      ***** WARNING *****
>   Using default Cxx optimization flags "-O". You might consider manually setting optimal
>   optimization flags for your system with CXXOPTFLAGS="optimization flags" see
>   config/examples/arch-*-opt.py for examples
> =============================================================================================
> TESTING: checkCxxLibraries from config.compilers(config/BuildSystem/config/compilers.py:450)
> *********************************************************************************************
>            UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):
> ---------------------------------------------------------------------------------------------
>   Cxx libraries cannot directly be used with C as linker.
>   If you don't need the C++ compiler to build external packages or for you application you
>   can run
>   ./configure with --with-cxx=0. Otherwise you need a different combination of C and C++
>   compilers
> *********************************************************************************************
>  
> makefile:24: /cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscrules: No such file or directory
> make[1]: *** No rule to make target '/cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscrules'.  Stop.
> gmakefile:67: arch-mswin-c-opt/lib/petsc/conf/files: No such file or directory
> make: *** [GNUmakefile:17: /cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/include/petscconf.h] Error 2
> makefile:24: /cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscrules: No such file or directory
> make[1]: *** No rule to make target '/cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscrules'.  Stop.
> /cygdrive/e/petsc-v3.19.2/lib/petsc/conf/variables:140: /cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscvariables: No such file or directory
> make: *** [GNUmakefile:17: /cygdrive/e/petsc-v3.19.2/arch-mswin-c-opt/lib/petsc/conf/petscvariables] Error 2

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20230601/da324c16/attachment.html>


More information about the petsc-users mailing list