[petsc-users] Something went wrong with PETSc after installing ParaView
Matthew Knepley
knepley at gmail.com
Sat Aug 5 07:22:58 CDT 2023
On Sat, Aug 5, 2023 at 3:22 AM K. Wu <wuktsinghua at gmail.com> 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/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20230805/476e9402/attachment.html>
More information about the petsc-users
mailing list