<html><head></head><body><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;"></div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;">
</div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false">My program finally worked after built with Petsc-3.12.4 and its include files (obviously I missed the latter and still used Petsc-3.4.2's include files in my previous tests). </div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false"><br></div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false">The conclusion is that the old Petsc-3.4.2 does not work for Win-10.</div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false"><br></div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false">Thanks a lot for helps from Satish, Matt and Jacob!</div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false"><br></div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false">Regards,</div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;" dir="ltr" data-setdir="false">Qin </div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;"><br></div><div class="ydpdef65a9ayahoo-style-wrap" style="font-family: Helvetica Neue,Helvetica,Arial,sans-serif; font-size: 13px;">
</div><div class="ydp52c0ac0eyahoo_quoted" id="ydp52c0ac0eyahoo_quoted_6338215267">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, March 31, 2020, 01:59:03 PM CDT, Satish Balay <balay@mcs.anl.gov> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">What other dependencies?<br></div><div dir="ltr"><br></div><div dir="ltr">For an example makefile that compiles multiple sources into a single binary [using gnumake - which is what you have] - check<br></div><div dir="ltr"><br></div><div dir="ltr">src/ts/examples/tutorials/multirate/makefile<br></div><div dir="ltr"><br></div><div dir="ltr">Satish<br></div><div dir="ltr"><br></div><div dir="ltr">On Tue, 31 Mar 2020, Matthew Knepley wrote:<br></div><div dir="ltr"><br></div><div dir="ltr">> On Tue, Mar 31, 2020 at 2:42 PM Qin Lu via petsc-users <<br></div><div dir="ltr">> <a href="mailto:petsc-users@mcs.anl.gov" target="_blank" rel="nofollow">petsc-users@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> <br></div><div dir="ltr">> > My program has multiple files in a single directory, and there are some<br></div><div dir="ltr">> > other dependencies. Are you talking about /petsc-3.12.4/makefile? Is there<br></div><div dir="ltr">> > any instructions on how to compile my code using petsc makefile?<br></div><div dir="ltr">> ><br></div><div dir="ltr">> <br></div><div dir="ltr">> Yes, there is a chapter in the manual.<br></div><div dir="ltr">> <br></div><div dir="ltr">> Thanks,<br></div><div dir="ltr">> <br></div><div dir="ltr">> Matt<br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> > Thanks,<br></div><div dir="ltr">> > Qin<br></div><div dir="ltr">> ><br></div><div dir="ltr">> > On Tuesday, March 31, 2020, 12:16:31 PM CDT, Satish Balay <<br></div><div dir="ltr">> > <a href="mailto:balay@mcs.anl.gov" target="_blank" rel="nofollow">balay@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> ><br></div><div dir="ltr">> ><br></div><div dir="ltr">> > Is your code a single source file? multiple sourcefiles in a single dir?<br></div><div dir="ltr">> > any external dependencies other than petsc?<br></div><div dir="ltr">> ><br></div><div dir="ltr">> > If possible - try compiling your code with petsc makefile. Does the code<br></div><div dir="ltr">> > run correctly this way?<br></div><div dir="ltr">> ><br></div><div dir="ltr">> > Satish<br></div><div dir="ltr">> ><br></div><div dir="ltr">> > On Tue, 31 Mar 2020, Qin Lu via petsc-users wrote:<br></div><div dir="ltr">> ><br></div><div dir="ltr">> > > I built and tested ex1f.F90 and ex2f.F90, both call KSPCreate(), both<br></div><div dir="ltr">> > work well.<br></div><div dir="ltr">> > > My program is built using either MS Visual Studio or my own makefile.<br></div><div dir="ltr">> > Are there any special compilation/link options required for my program in<br></div><div dir="ltr">> > order to link with Petsc lib in Win-10?<br></div><div dir="ltr">> > > Thanks,Qin<br></div><div dir="ltr">> > > On Tuesday, March 31, 2020, 11:51:43 AM CDT, Satish Balay <<br></div><div dir="ltr">> > <a href="mailto:balay@mcs.anl.gov" target="_blank" rel="nofollow">balay@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > And use 'CHKERRA(ierr)' in your code to catch such failures early.<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > Refer to example src/ksp/ksp/examples/tutorials/ex7f.F90<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > >>>>>>>>><br></div><div dir="ltr">> > > call PetscInitialize(PETSC_NULL_CHARACTER,ierr)<br></div><div dir="ltr">> > > if (ierr /= 0) then<br></div><div dir="ltr">> > > write(6,*)'Unable to initialize PETSc'<br></div><div dir="ltr">> > > stop<br></div><div dir="ltr">> > > endif<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > call<br></div><div dir="ltr">> > PetscOptionsGetInt(PETSC_NULL_OPTIONS,PETSC_NULL_CHARACTER,'-m',m,flg,ierr)<br></div><div dir="ltr">> > > CHKERRA(ierr)<br></div><div dir="ltr">> > > <<<<<<<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > etc..<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > Satish<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > On Tue, 31 Mar 2020, Satish Balay via petsc-users wrote:<br></div><div dir="ltr">> > ><br></div><div dir="ltr">> > > > Try PETSc examples with KSPCreate() - do they run correctly?<br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > > > How do you build your code - do you use petsc formatted makefile?<br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > > > Look for differences. Also run your code in valgrind on linux. Or you<br></div><div dir="ltr">> > need to debug further on windows..<br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > > > Satish<br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > > > On Tue, 31 Mar 2020, Qin Lu via petsc-users wrote:<br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > In the MS Visual Studio debugger, I can see there are 2 calls<br></div><div dir="ltr">> > before KSPSetType:<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > call PetscInitialize(PETSC_NULL_CHARACTER,ierr)<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > call KSPCreate(PETSC_COMM_WORLD,ksp_solver,ierr)<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > It turns out KSPCreate returns ierr=1, so it is the first Petsc call<br></div><div dir="ltr">> > that got error.<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > My program in Linux (also built with Intel compilers 2018) works<br></div><div dir="ltr">> > without problem.<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > Thanks,<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > Qin<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > On Tuesday, March 31, 2020, 11:01:56 AM CDT, Satish Balay <<br></div><div dir="ltr">> > <a href="mailto:balay@mcs.anl.gov" target="_blank" rel="nofollow">balay@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > Do PETSc examples that use KSPSetType() say<br></div><div dir="ltr">> > src/ksp/ksp/tutorials/ex7f.F90 compile/run with this install?<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > Its probably best to run your code in a debugger to determine the<br></div><div dir="ltr">> > problem.<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > [If your code can compile on linux - I'll also suggest running it<br></div><div dir="ltr">> > with valgrind]<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > Satish<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > On Tue, 31 Mar 2020, Qin Lu wrote:<br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > > > > Hello,<br></div><div dir="ltr">> > > > > > I moved Intel-MPI libs to a directory without space, now the<br></div><div dir="ltr">> > configuration/build of Petsc-3.12.4 worked with Intel-MPI, and test of ex2<br></div><div dir="ltr">> > worked well with mpiexec. However, my Fortran-90 program linked with this<br></div><div dir="ltr">> > Petsc lib still crashed at calling KSPSetType(ksp_solver,KSPBCGS,ierr),<br></div><div dir="ltr">> > same as what happened when using MPICH2. I suspect the issue is not in MPI,<br></div><div dir="ltr">> > but in how Petsc is configured/built in Windows-10 using Intel compilers<br></div><div dir="ltr">> > (the same program in Win-7 works without problem). The configuration is<br></div><div dir="ltr">> > attached below.<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > Do you any suggestions how to proceed?<br></div><div dir="ltr">> > > > > > Thanks,Qin<br></div><div dir="ltr">> > > > > > ============./configure --with-cc='win32fe icl' --with-fc='win32fe<br></div><div dir="ltr">> > ifort' --with-cxx='win32fe icl'<br></div><div dir="ltr">> > --with-petsc-arch="arch-win64-release-intel-mpi"<br></div><div dir="ltr">> > --prefix=/cygdrive/c/cygwin_cache/petsc-3.12.4-release-win-64bit-intel-mpi<br></div><div dir="ltr">> > --with-blas-lapack-dir="/cygdrive/c/Program Files<br></div><div dir="ltr">> > (x86)/IntelSWTools/compilers_and_libraries_2018.5.274/windows/mkl/lib/intel64"<br></div><div dir="ltr">> > --with-mpi-include="/cygdrive/c/cygwin_cache/Intel-mpi-2019.6.166/intel64/include"<br></div><div dir="ltr">> > --with-mpi-lib="/cygdrive/c/cygwin_cache/Intel-mpi-2019.6.166/intel64/lib/release/impi.lib"<br></div><div dir="ltr">> > --with-mpi-compilers=0--with-debugging=0 --useThreads=0 --with-x=0<br></div><div dir="ltr">> > --with-x11=0 --with-xt=0 --with-shared-libraries=0<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > On Tuesday, March 31, 2020, 08:39:01 AM CDT, Satish Balay via<br></div><div dir="ltr">> > petsc-users <<a href="mailto:petsc-users@mcs.anl.gov" target="_blank" rel="nofollow">petsc-users@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > On Mon, 30 Mar 2020, Jacob Faibussowitsch wrote:<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > > >> We just cannot cope with spaces in paths. Can you use the<br></div><div dir="ltr">> > shortened<br></div><div dir="ltr">> > > > > > > >> contiguous name instead of "Program File"?<br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > > > FYI: Program Files or Program Files(x86) is where windows<br></div><div dir="ltr">> > installs all of its applications (from OS or installed by user). It is best<br></div><div dir="ltr">> > to install your MPI and other packages in root dir C:. Thats why for<br></div><div dir="ltr">> > example MinGW installs itself in there, so it doesn’t have to deal with the<br></div><div dir="ltr">> > space in the path.<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > No need to do this alternate install if using cygpath - as per<br></div><div dir="ltr">> > installation instructions<br></div><div dir="ltr">> > <a href="https://www.mcs.anl.gov/petsc/documentation/installation.html" target="_blank" rel="nofollow">https://www.mcs.anl.gov/petsc/documentation/installation.html</a><br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > Satish<br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > > > Best regards,<br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > > > Jacob Faibussowitsch<br></div><div dir="ltr">> > > > > > > (Jacob Fai - booss - oh - vitch)<br></div><div dir="ltr">> > > > > > > Cell: (312) 694-3391<br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > > > > On Mar 30, 2020, at 9:18 PM, Satish Balay via petsc-users <<br></div><div dir="ltr">> > <a href="mailto:petsc-users@mcs.anl.gov" target="_blank" rel="nofollow">petsc-users@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > > On Mon, 30 Mar 2020, Matthew Knepley wrote:<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > >> On Mon, Mar 30, 2020 at 9:28 PM Qin Lu <<a href="mailto:lu_qin_2000@yahoo.com" target="_blank" rel="nofollow">lu_qin_2000@yahoo.com</a>><br></div><div dir="ltr">> > wrote:<br></div><div dir="ltr">> > > > > > > >><br></div><div dir="ltr">> > > > > > > >>> Hi,<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> I installed Intel-MPI 2019, and configured petsc-3.12.4 using<br></div><div dir="ltr">> > > > > > > >>> --with-mpi-dir="/cygdrive/c/Program Files<br></div><div dir="ltr">> > > > > > > >>> (x86)/IntelSWTools/mpi/2019.6.166/intel64", it didn't work.<br></div><div dir="ltr">> > So I change to<br></div><div dir="ltr">> > > > > > > >>> use --with-mpi-include and --with-mpi-lib, still didn't<br></div><div dir="ltr">> > work. The<br></div><div dir="ltr">> > > > > > > >>> config.log is attached.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> The following is my configuration:<br></div><div dir="ltr">> > > > > > > >>> ===============<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> ./configure --with-cc='win32fe icl' --with-fc='win32fe ifort'<br></div><div dir="ltr">> > > > > > > >>> --with-cxx='win32fe icl'<br></div><div dir="ltr">> > --with-petsc-arch="arch-win64-release-intel-mpi"<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > --prefix=/cygdrive/c/cygwin_cache/petsc-3.12.4-release-win-64bit-intel-mpi<br></div><div dir="ltr">> > > > > > > >>> --with-blas-lapack-dir="/cygdrive/c/Program Files<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > (x86)/IntelSWTools/compilers_and_libraries_2018.5.274/windows/mkl/lib/intel64"<br></div><div dir="ltr">> > > > > > > >>> --with-mpi-include="/cygdrive/c/Program Files<br></div><div dir="ltr">> > > > > > > >>> (x86)/IntelSWTools/mpi/2019.6.166/intel64/include"<br></div><div dir="ltr">> > --with-mpi-lib="/cygdrive/c/Program<br></div><div dir="ltr">> > > > > > > >>> Files<br></div><div dir="ltr">> > (x86)/IntelSWTools/mpi/2019.6.166/intel64/lib/impicxx.lib" --with-<br></div><div dir="ltr">> > > > > > > >>> mpi-compilers=0 --with-debugging=0 --useThreads=0 --with-x=0<br></div><div dir="ltr">> > --with-x11=0<br></div><div dir="ltr">> > > > > > > >>> --with-xt=0 --with-shared-libraries=0<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> =============<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Thanks for any suggestions.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >> We just cannot cope with spaces in paths. Can you use the<br></div><div dir="ltr">> > shortened<br></div><div dir="ltr">> > > > > > > >> contiguous name instead of "Program File"?<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > > Yeah - the config/examples/arch-ci-mswin*.py lists paths<br></div><div dir="ltr">> > without spaces - and <a href="https://www.mcs.anl.gov/petsc/documentation/installation.html" target="_blank" rel="nofollow">https://www.mcs.anl.gov/petsc/documentation/installation.html</a><br></div><div dir="ltr">> > <<a href="https://www.mcs.anl.gov/petsc/documentation/installation.html" target="_blank" rel="nofollow">https://www.mcs.anl.gov/petsc/documentation/installation.html</a>> has the<br></div><div dir="ltr">> > instructions<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > > The way to get this is: (for example)<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > > <a href="mailto:balay@ps5" target="_blank" rel="nofollow">balay@ps5</a> ~<br></div><div dir="ltr">> > > > > > > > $ cygpath -u `cygpath -ms '/cygdrive/C/Program Files/Microsoft<br></div><div dir="ltr">> > MPI/Bin/mpiexec'`<br></div><div dir="ltr">> > > > > > > > /cygdrive/c/PROGRA~1/MICROS~2/Bin/mpiexec.exe<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > > Satish<br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > ><br></div><div dir="ltr">> > > > > > > >><br></div><div dir="ltr">> > > > > > > >> Thanks,<br></div><div dir="ltr">> > > > > > > >><br></div><div dir="ltr">> > > > > > > >> Matt<br></div><div dir="ltr">> > > > > > > >><br></div><div dir="ltr">> > > > > > > >>> Regards,<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Qin<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> On Monday, March 30, 2020, 04:15:14 PM CDT, Matthew Knepley <<br></div><div dir="ltr">> > > > > > > >>> <a href="mailto:knepley@gmail.com" target="_blank" rel="nofollow">knepley@gmail.com</a>> wrote:<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> On Mon, Mar 30, 2020 at 4:43 PM Qin Lu via petsc-users <<br></div><div dir="ltr">> > > > > > > >>> <a href="mailto:petsc-users@mcs.anl.gov" target="_blank" rel="nofollow">petsc-users@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Hi Satish,<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> The ex2.exe works with "mpiexec -np 2" when I ran it from<br></div><div dir="ltr">> > command line.<br></div><div dir="ltr">> > > > > > > >>> Then I ran "which mpiexec", it actually points to Intel-MPI<br></div><div dir="ltr">> > instead of<br></div><div dir="ltr">> > > > > > > >>> MPICH2, probably because I have set the former's path in<br></div><div dir="ltr">> > environment<br></div><div dir="ltr">> > > > > > > >>> variable PATH in Win-10. I will try to reinstall Intel-MPI<br></div><div dir="ltr">> > and build Petsc<br></div><div dir="ltr">> > > > > > > >>> with Intel-MPI.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> As for the crash of calling to<br></div><div dir="ltr">> > KSPSetPCSide(ksp_solver,PC_RIGHT,ierr) in<br></div><div dir="ltr">> > > > > > > >>> my Fortran-90 program, do you have any idea what can be<br></div><div dir="ltr">> > wrong? Can it be<br></div><div dir="ltr">> > > > > > > >>> related to MPI?<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> I tested config/examples/arch-ci-mswin-intel.py as you<br></div><div dir="ltr">> > suggested, but got<br></div><div dir="ltr">> > > > > > > >>> the following output:<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> ============<br></div><div dir="ltr">> > > > > > > >>> python ./arch-ci-mswin-intel.py<br></div><div dir="ltr">> > > > > > > >>> Traceback (most recent call last):<br></div><div dir="ltr">> > > > > > > >>> File "./arch-ci-mswin-intel.py", line 10, in <module><br></div><div dir="ltr">> > > > > > > >>> import configure<br></div><div dir="ltr">> > > > > > > >>> ImportError: No module named configure<br></div><div dir="ltr">> > > > > > > >>> ============<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> You have to run those from $PETSC_DIR.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Matt<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Thanks,<br></div><div dir="ltr">> > > > > > > >>> Qin<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> I will try to use Intel-MPI and see what will happen.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Thanks,<br></div><div dir="ltr">> > > > > > > >>> Qin<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> On Monday, March 30, 2020, 01:47:49 PM CDT, Satish Balay <<br></div><div dir="ltr">> > > > > > > >>> <a href="mailto:balay@mcs.anl.gov" target="_blank" rel="nofollow">balay@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Please preserve cc: to the list<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>>> shared libraries: disabled<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> So PETSc is correctly built as static.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>>>> C:/Program Files/mpich2x64/bin/mpiexec.exe: error while<br></div><div dir="ltr">> > loading shared<br></div><div dir="ltr">> > > > > > > >>> libraries: ?: cannot open shared object file: No such file<br></div><div dir="ltr">> > or directory<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> So its not clear which shared library this error is<br></div><div dir="ltr">> > referring to. But then<br></div><div dir="ltr">> > > > > > > >>> - this error was with petsc-3.4.2<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> You can always try to run the code manually without mpiexec<br></div><div dir="ltr">> > - and see if<br></div><div dir="ltr">> > > > > > > >>> that works.<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> cd src/ksp/ksp/examples/tutorials<br></div><div dir="ltr">> > > > > > > >>> make ex2<br></div><div dir="ltr">> > > > > > > >>> ./ex2<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Wrt MSMPI - yes its free to download<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> And PETSc does work with Intel-MPI. It might be a separate<br></div><div dir="ltr">> > > > > > > >>> download/install. [so I can't say if what you have is the<br></div><div dir="ltr">> > correct install<br></div><div dir="ltr">> > > > > > > >>> of IntelMPI or not]<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Check the builds we use for testing - for ex:<br></div><div dir="ltr">> > > > > > > >>> config/examples/arch-ci-mswin-*.py<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> Satish<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> On Mon, 30 Mar 2020, Qin Lu wrote:<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>>> Hi Satish,<br></div><div dir="ltr">> > > > > > > >>>> The configure.log and RDict.log of Petsc-3.12.4 build is<br></div><div dir="ltr">> > attached.<br></div><div dir="ltr">> > > > > > > >>>> Is the MSMPI free to use in Windows-10?<br></div><div dir="ltr">> > > > > > > >>>> Does Petsc support Intel-MPI? I have it in my machine, but<br></div><div dir="ltr">> > for some<br></div><div dir="ltr">> > > > > > > >>> reason I only find the /mpi/intel64/bin, but not<br></div><div dir="ltr">> > /mpi/intel64/include<br></div><div dir="ltr">> > > > > > > >>> subdirectory of it.<br></div><div dir="ltr">> > > > > > > >>>> Thanks a lot for your help.Qin<br></div><div dir="ltr">> > > > > > > >>>> On Monday, March 30, 2020, 12:26:09 PM CDT, Satish Balay <<br></div><div dir="ltr">> > > > > > > >>> <a href="mailto:balay@mcs.anl.gov" target="_blank" rel="nofollow">balay@mcs.anl.gov</a>> wrote:<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> MPICH is unsupported - and we haven't tested with it for a<br></div><div dir="ltr">> > long time.<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> And petsc-3.4.2 is from 2013 - and untested with current gen<br></div><div dir="ltr">> > > > > > > >>> os/compilers/libraries.<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> Can you send logs from Petsc-3.12.4 build [or try latest<br></div><div dir="ltr">> > Petsc-3.13.0]?<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> We recommend 64bit MSMPI for windows.<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> Satish<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>> On Mon, 30 Mar 2020, Qin Lu via petsc-users wrote:<br></div><div dir="ltr">> > > > > > > >>>><br></div><div dir="ltr">> > > > > > > >>>>> Hello,<br></div><div dir="ltr">> > > > > > > >>>>> I am trying to build Petsc-3.4.2 in my Windows-10<br></div><div dir="ltr">> > workstation using<br></div><div dir="ltr">> > > > > > > >>> Cygwin, with Intel-2018 compilers and MKL, and MPICH2. The<br></div><div dir="ltr">> > > > > > > >>> configuration/compilation/installation seem to finish<br></div><div dir="ltr">> > without problem, but<br></div><div dir="ltr">> > > > > > > >>> test program (ex19) failed since it could not find a shared<br></div><div dir="ltr">> > lib. Then I<br></div><div dir="ltr">> > > > > > > >>> linked the libpetsc.lib with my program (in Fortran-90), but<br></div><div dir="ltr">> > it got run<br></div><div dir="ltr">> > > > > > > >>> time crash when it calls<br></div><div dir="ltr">> > KSPSetPCSide(ksp_solver,PC_RIGHT,ierr) or other<br></div><div dir="ltr">> > > > > > > >>> Petsc subroutines. Note that this package was built, tested<br></div><div dir="ltr">> > and worked well<br></div><div dir="ltr">> > > > > > > >>> with the same Fortran-90 program in my Windows-7 workstation.<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Also tried Petsc-3.12.4 but got the same errors.<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> The following is my configuration:<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> ===============<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> ./configure --with-cc='win32fe icl' --with-fc='win32fe<br></div><div dir="ltr">> > ifort'<br></div><div dir="ltr">> > > > > > > >>> --with-cxx='win32fe icl'<br></div><div dir="ltr">> > --with-petsc-arch="arch-win64-release"<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > --prefix=/cygdrive/c/cygwin_cache/petsc-3.4.2-release-win-64bit<br></div><div dir="ltr">> > > > > > > >>> --with-blas-lapack-dir="/cygdrive/c/Program Files<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > (x86)/IntelSWTools/compilers_and_libraries_2018.5.274/windows/mkl/lib/intel64"<br></div><div dir="ltr">> > > > > > > >>> --with-mpi-dir="/cygdrive/c/Program Files/mpich2x64"<br></div><div dir="ltr">> > --with-debugging=0<br></div><div dir="ltr">> > > > > > > >>> --useThreads=0 --with-x=0 --with-x11=0 --with-xt=0<br></div><div dir="ltr">> > --with-shared-libraries=0<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> ===============<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> The error message of running ex19 is:<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> =================<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> $ make<br></div><div dir="ltr">> > PETSC_DIR=/cygdrive/c/cygwin_cache/petsc-3.4.2-debug-win-64bit<br></div><div dir="ltr">> > > > > > > >>> test<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Running test examples to verify correct installation<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Using<br></div><div dir="ltr">> > PETSC_DIR=/cygdrive/c/cygwin_cache/petsc-3.4.2-debug-win-64bit<br></div><div dir="ltr">> > > > > > > >>> and PETSC_ARCH=arch-win64-debug<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Possible error running C/C++<br></div><div dir="ltr">> > src/snes/examples/tutorials/ex19 with 1<br></div><div dir="ltr">> > > > > > > >>> MPI process<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> See <a href="http://www.mcs.anl.gov/petsc/documentation/faq.html" target="_blank" rel="nofollow">http://www.mcs.anl.gov/petsc/documentation/faq.html</a><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> C:/Program Files/mpich2x64/bin/mpiexec.exe: error while<br></div><div dir="ltr">> > loading shared<br></div><div dir="ltr">> > > > > > > >>> libraries: ?: cannot open shared object file: No such file<br></div><div dir="ltr">> > or directory<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> =================<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Thanks a lot for any suggestions.<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Best Regards,<br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>> Qin<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>>>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> --<br></div><div dir="ltr">> > > > > > > >>> What most experimenters take for granted before they begin<br></div><div dir="ltr">> > their<br></div><div dir="ltr">> > > > > > > >>> experiments is infinitely more interesting than any results<br></div><div dir="ltr">> > to which their<br></div><div dir="ltr">> > > > > > > >>> experiments lead.<br></div><div dir="ltr">> > > > > > > >>> -- Norbert Wiener<br></div><div dir="ltr">> > > > > > > >>><br></div><div dir="ltr">> > > > > > > >>> <a href="https://www.cse.buffalo.edu/~knepley/" target="_blank" rel="nofollow">https://www.cse.buffalo.edu/~knepley/</a><br></div><div dir="ltr">> > > > > > > >>> <<a href="http://www.cse.buffalo.edu/~knepley/ " target="_blank" rel="nofollow">http://www.cse.buffalo.edu/~knepley/ </a><<br></div><div dir="ltr">> > <a href="http://www.cse.buffalo.edu/~knepley/" target="_blank" rel="nofollow">http://www.cse.buffalo.edu/~knepley/</a>>><br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > > ><br></div><div dir="ltr">> > > > > ><br></div><div dir="ltr">> > > > ><br></div><div dir="ltr">> > > ><br></div><div dir="ltr">> > ><br></div><div dir="ltr">> ><br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div><div dir="ltr">> <br></div></div>
</div>
</div></body></html>