[petsc-users] 回复: out of date warning when petscmpiexec.

Syvshc syvshc at foxmail.com
Thu Dec 15 12:21:23 CST 2022


I got lots of build information, 
and after "make -f gmakefile libs", the out of date warning of petscmpiexec was gone. 


❯ petscmpiexec -n 1 ./e
Warning: ************** The executable ./e is out of date
e is about 1.000000000000000
rank 0 did 0 flops



BTW, if I want to know something of the "executable out of date" question, 
should I send a new mail or I can just ask under these mails?


Thanks for your help sincerely.


Syvshc




------------------ 原始邮件 ------------------
发件人:                                                                                                                        "petsc-users"                                                                                    <balay at mcs.anl.gov>;
发送时间: 2022年12月16日(星期五) 凌晨2:11
收件人: "Syvshc"<syvshc at foxmail.com>;
抄送: "petsc-users"<petsc-users at mcs.anl.gov>;
主题: Re: [petsc-users] out of date warning when petscmpiexec.



> make -q -f gmakefile libs
> echo $?
> 1

So "make" does think the library is out-of-date. If up-to-date - you should see a '0' - not '1'. One more try:

what do you get for:

cd $PETSC_DIR
make -f gmakefile libs  # i.e without -q

Satish

On Fri, 16 Dec 2022, Syvshc wrote:

> I still get this warning, I found that "make -q" command won't get any respond.
> 
> 
> Here is the whole output:
> 
> 
> ?7?9 cd $PETSC_DIR
> make -q -f gmakefile libs
> echo $?
> cd ~/git/p4pdes/c/ch1
> make -q e
> echo $?
> petscmpiexec -n 1 ./e
> make clean
> make e
> make -q e
> echo $?
> petscmpiexec -n 1 ./e
> 1
> 1
> Warning: ************** The PETSc libraries are out of date
> Warning: ************** The executable ./e is out of date
> e is about 1.000000000000000
> rank 0 did 0 flops
> mpicc -o e.o -c -fPIC -Wall -Wwrite-strings -Wno-unknown-pragmas -Wno-lto-type-mismatch -Wno-stringop-overflow -fstack-protector -fvisibility=hidden -g3 -O0 -pedantic -std=c99 -I/home/syvshclily/git/petsc/petsc-latest/include -I/home/syvshclily/git/petsc/petsc-latest/arch-linux-c-debug/include&nbsp; &nbsp; `pwd`/e.c
> mpicc -fPIC -Wall -Wwrite-strings -Wno-unknown-pragmas -Wno-lto-type-mismatch -Wno-stringop-overflow -fstack-protector -fvisibility=hidden -g3 -O0 -pedantic -std=c99 -o e e.o&nbsp; -Wl,-rpath,/home/syvshclily/git/petsc/petsc-latest/arch-linux-c-debug/lib -L/home/syvshclily/git/petsc/petsc-latest/arch-linux-c-debug/lib -Wl,-rpath,/home/syvshclily/git/petsc/petsc-latest/arch-linux-c-debug/lib -L/home/syvshclily/git/petsc/petsc-latest/arch-linux-c-debug/lib -Wl,-rpath,/usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0 -L/usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0 -lpetsc -lsuperlu_dist -llapack -lblas -lm -lX11 -lstdc++ -ldl -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi -lgfortran -lm -lgfortran -lm -lgcc_s -lquadmath -lstdc++ -ldl
> /usr/sbin/rm -f e.o
> 1
> Warning: ************** The PETSc libraries are out of date
> Warning: ************** The executable ./e is out of date
> e is about 1.000000000000000
> rank 0 did 0 flops
> 
> 
> 
> Thanks for your reply.&nbsp;
> 
> 
> Syvshc
> 
> 
> 
> 
> ------------------&nbsp;Original&nbsp;------------------
> From:                                                                                                                        "petsc-users"                                                                                    <balay at mcs.anl.gov&gt;;
> Date:&nbsp;Fri, Dec 16, 2022 01:40 AM
> To:&nbsp;"Syvshc"<syvshc at foxmail.com&gt;;
> Cc:&nbsp;"petsc-users"<petsc-users at mcs.anl.gov&gt;;
> Subject:&nbsp;Re: [petsc-users] out of date warning when petscmpiexec.
> 
> 
> 
> That's strange. Do you still get this warning from petscmpiexec?
> 
> Can you run these commands - and copy/paste the *complete* session from your terminal [for these commands and their output on terminal] ?
> 
> &gt;&gt;&gt;&gt;&gt;&gt;
> cd $PETSC_DIR
> make -q -f gmakefile libs
> echo $?
> cd bueler/p4pdes
> make -q e
> echo $?
> petscmpiexec -n 1 ./e
> make clean
> make e
> make -q e
> echo $?
> petscmpiexec -n 1 ./e
> <<<<
> 
> Alternatively you can just use mpiexec [ i.e not use petscmpiexec - its just a convenience wrapper over using correct mpiexec/valgrind].
> 
> Satish
> 
> On Fri, 16 Dec 2022, Syvshc wrote:
> 
> &gt; I run this command in the root dir of my petsc, and didn't get any response.
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; ------------------&amp;nbsp;Original&amp;nbsp;------------------
> &gt; From:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "petsc-users"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <balay at mcs.anl.gov&amp;gt;;
> &gt; Date:&amp;nbsp;Thu, Dec 15, 2022 10:19 PM
> &gt; To:&amp;nbsp;"Syvshc"<syvshc at foxmail.com&amp;gt;;
> &gt; Cc:&amp;nbsp;"petsc-users"<petsc-users at mcs.anl.gov&amp;gt;;
> &gt; Subject:&amp;nbsp;Re: [petsc-users] out of date warning when petscmpiexec.
> &gt; 
> &gt; 
> &gt; 
> &gt; What do you get - if you invoke the following command in petsc source dir?
> &gt; 
> &gt; make -q -f gmakefile libs
> &gt; 
> &gt; [this is the test petscmpiexec is using to check if "libraries are out of date"]
> &gt; 
> &gt; Satish
> &gt; 
> &gt; On Thu, 15 Dec 2022, Syvshc wrote:
> &gt; 
> &gt; &amp;gt; I'm a beginner with petsc, and I'm reading&amp;amp;nbsp;PETSc for Partial Differential Equations.&amp;amp;nbsp;
> &gt; &amp;gt; 
> &gt; &amp;gt; There is the newest release version (3.18.2) of PETSc's gitlab repo on my device, and openmpi in my system (/usr/sbin/).&amp;amp;nbsp;
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; Here is the repo and what I tried to compiling.&amp;amp;nbsp;p4pdes/e.c at master ?? bueler/p4pdes (github.com)
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; After "make e", I got an excutable file "e". "./e" or "mpiexec -n 4 ./e" can perfectly run.&amp;amp;nbsp;
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; However when I use "petscmpiexec -n 4 ./e", I got some warnings:
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; Warning: ************** The PETSc libraries are out of date
> &gt; &amp;gt; Warning: ************** The executable ./e is out of date
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; What should I do to fix the warning?
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; Also this is the first time that I send to a mail-list, if there are some mistakes I made, please tell me.&amp;amp;nbsp;
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; Kind regards,
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; Syvshc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20221216/27d28efd/attachment-0001.html>


More information about the petsc-users mailing list