Dear Matthew, Thanks for your reply!
Is there any way that I can choose to use the previous MPI installation used to build PETSc? Regards, Kai Matthew Knepley <[email protected]> 于2023年8月5日周六 14:23写道： > On Sat, Aug 5, 2023 at 3:22 AM K. Wu <[email protected]> wrote: > >> Hi all, >> >> Good day! >> >> After installing ParaView on my desktop, PETSc starts to work anomalously >> even after reconfiguration: >> 1. If I use mpirun (frequently used before), it seems that now all the >> processors will run the program independently without communication. While >> mpiexec seems to work properly. >> > > Yes, this indicates that the "mpirun" is from a different installation of > MPI than "mpiexec", which seems to be from the MPI installation used to > build PETSc. Probably the Paraview package installed its own MPI package. > > >> >> 2. The Makefile (as attached) which works fine before starts to complain: >> make: *** No rule to make target 'chkopts', needed by 'test'. Stop. >> > > The 'chkopts' target is defined in the toplevel PETSc makefile, but it is > deprecated. You can take it out. > > Thanks, > > Matt > > >> Thanks for your kind help! >> >> Best regards, >> Kai >> >> >> PETSC_DIR=~/petsc >> PETSC_ARCH=arch-linux-c-debug >> CFLAGS = -I. >> FFLAGS= >> CPPFLAGS=-I. >> FPPFLAGS= >> LOCDIR= >> EXAMPLESC= >> EXAMPLESF= >> MANSEC= >> CLEANFILES= >> NP= >> >> >> include ${PETSC_DIR}/lib/petsc/conf/variables >> include ${PETSC_DIR}/lib/petsc/conf/rules >> include ${PETSC_DIR}/lib/petsc/conf/test >> >> test: ex2-2.o chkopts >> rm -rf topopt >> -${CLINKER} -o test ex2-2.o ${PETSC_SYS_LIB} >> ${RM} ex2-2.o >> rm -rf *.o >> > > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ > <http://www.cse.buffalo.edu/~knepley/> >
