The compiler is burping out some warning message which confuses configure into thinking there is a problem.
cl: ������ warning D9035 :��experimental:preprocessor��ѡ���ѷ���������ڽ����İ汾���Ƴ� cl: ������ warning D9036 :ʹ�á�Zc:preprocessor������ʹ�á�experimental:preprocessor�� cl: ������ warning D9002 :����δ֪ѡ�-Qwd10161��: Any chance you can use a more recent version of VS. If not, we'll need to send you a file for the warning message. > On Mar 2, 2023, at 9:12 PM, 冯上玮 <[email protected]> wrote: > > Hi, > > This time I try with ./configure --with-cc='win32fe cl' --with-fc=0 > --with-cxx='win32fe cl' --download-f2cblaslapack, without fortran may have no > problem in consideration that other libs will be used are CGNS and METIS. > > Unfortunately, however, another error appeared as: > > 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 > > The attachment is the log file, but some parts are unreadable. > > Thanks for your continuous aid! > ------------------ Original ------------------ > From: "Satish Balay"<[email protected]>; > Date: Fri, Mar 3, 2023 02:13 AM > To: "冯上玮"<[email protected]>; > Cc: "petsc-users"<[email protected]>; > Subject: Re: [petsc-users] Error in configuring PETSc with Cygwin > > On Fri, 3 Mar 2023, 冯上玮 wrote: > > > Hi team, > > > > > > Recently I try to install PETSc with Cygwin since I'd like to use PETSc > > with Visual Studio on Windows10 plateform. For the sake of clarity, I > > firstly list the softwares/packages used below: > > > > > > 1. PETSc: version 3.18.5 > > 2. VS: version 2019 > > 3. Intel Parallel Studio XE: version 2020 > > 4. Cygwin with py3.8 and make (and default installation) > > > > > > And because I plan to use Intel mpi, the compiler option in configuration > > is: > > > > > > ./configure --with-cc='win32fe cl' --with-fc='win32fe ifort' > > --with-cxx='win32fe cl' --download-fblaslapack > > Check config/examples/arch-ci-mswin-opt-impi.py for an example on specifying > IMPI [and MKL - instead of fblaslapack]. And if you don't need MPI - you can > use --with-mpi=0 > > > > > > > where there is no option for mpi. > > > > > > While the PROBLEM came with the compiler option --with-fc='win32fe ifort', > > which returned an error (or two) as: > > > > > > 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 > > '/cygdrive/d/petsc/petsc-3.18.5/lib/petsc/bin/win32fe/win32fe ifort'? > > If you are not using PETSc from fortran - you don't need ifort. You can use > --with-fc=0 [with MKL or --download-f2cblaslapack] > > If you are still encountering errors - send us configure.log for the failed > build. > > Satish > > > > > > > > > Note that both ifort of x64 and ifort of ia-32 ended with the same error > > above and I install IPS with options related to mkl and fblaslapack. > > Something a bit suspectable is that I open Cygwin with dos. (actually the > > Intel Compiler 19.1 Update 3 Intel 64 Visual Studio 2019, x86 environment > > for the test of ifort ia-32 ,in particularlly) > > > > > > Therefore, I write this e-mail to you in order to confirm if I should add > > "--with-batch" or the error is caused by other reason, such as ifort ? > > > > > > Looking forward your reply! > > > > > > Sinserely, > > FENG. > > <configure.txt>
