May 2007 - petsc-dev - mailman3.cels.anl.gov

New PETSc release 2.3.3
by Barry Smith 24 May '07

24 May '07

---------------------------------------------------------------------------- Portable, Extensible Toolkit for Scientific Computation (PETSc) ---------------------------------------------------------------------------- http://www.mcs.anl.gov/petsc We are pleased to announce the release of the PETSc 2.3.3 parallel software libraries for the implicit solution of PDEs and related problems. There are a couple of MAJOR interface changes, listed at http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/changes/233.html please check these changes before compiling your codes. In particular the calling sequence for VecScatterBegin/End() now takes the scatter context as the first argument not the last. You can download from http://www-unix.mcs.anl.gov/petsc/petsc-as/download/index.html and and the installataion instructions are at http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/installation.html As always, please send bug reports, questions, and requests for new features to petsc-maint(a)mcs.anl.gov Thanks for your continued support. The PETSc developers, Satish, Lisandro, Matt, Victor, Barry and Hong

1 0

Re: change to VecScatterBegin/End
by Mark Adams 18 May '07

18 May '07

Satish, this is done, I compiled the library, but did not test it, and did NOT change the version number (the current version is already associated with the dev version as I recall). Mark On May 8, 2007, at 11:19 PM, Satish Balay wrote: > > The prototypes for VecScatterBegin() and VecScatterEnd() are now > changed. This change is made to have these routines consistant with > PETSc calling convention [i.e the first argument should be the > appropriate object for that functionality]. i.e: > > PetscErrorCode VecScatterBegin > (Vec,Vec,InsertMode,ScatterMode,VecScatter); > to > PetscErrorCode VecScatterBegin > (VecScatter,Vec,Vec,InsertMode,ScatterMode); > > Satish > > ********************************************************************** Mark Adams Ph.D. Columbia University 289 Engineering Terrace MC 4701 New York NY 10027 adams(a)pppl.gov www.columbia.edu/~ma2325 voice: 212.854.4485 fax: 212.854.8257 **********************************************************************

1 0

Re: Sun Studio Performance Library
by Yi-Feng Adam Zhang 17 May '07

17 May '07

Hi Satish, Thanks for your input. I will try to debug it and discuss with the petsc-maint alias. Regards, Adam Satish Balay wrote: > We have it working on a solaris [sparc] box - so I'm not sure what the > problem here is.. > > You can run this in a debugger to chek where it crashing.. If you have > -lsunperf, configure shoul automatically detect it [so no extra option > is necessary] > > Also - looks like -lsunperf requires -lsunmath -lm - so perhaps these > need specifying? > > [petsc-dev(a)mcs.anl.gov is not an appropriate list for such > discussions. You can send these issues to petsc-maint(a)mcs.anl.gov. If > you wish to discuss thse issues in a public list - then you can use > petsc-users(a)mcs.anl.gov list] > > Satish > > On Wed, 16 May 2007, Yi-Feng Adam Zhang wrote: > > >> Hi all, >> >> Does anyone use the latest Sun Studio Performance Library(libsunperf.a) with >> PETSc? I just make a compilation but failed in the test stage. >> >> The configure.py is : >> #!/usr/bin/env python >> if __name__ == '__main__': >> import sys >> sys.path.insert(0, '/work/adam/petsc/perf.mpi.suncc.blas.c/config') >> import configure >> configure_options = ['--with-cc-cc', '--with-shared=0', '--download-mpich=1', >> '-PETSC_ARCH=solaris2.10-c-debug', >> '--with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so', '--with-fc=0'] >> configure.petsc_configure(configure_options) >> >> >> The error message I get after issue "make test": >> -bash-3.00# make test >> Running test examples to verify correct installation >> Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI >> processSee >> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html >> [cli_0]: aborting job: >> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 >> lid velocity = 0.0016, prandtl # = 1, grashof # = 1 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably >> memory access out of range >> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger >> [0]PETSC ERROR: or see >> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… >> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find >> memory corruption errors >> [0]PETSC ERROR: likely location of problem given in stack below >> [0]PETSC ERROR: --------------------- Stack Frames >> ------------------------------------ >> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, >> [0]PETSC ERROR: INSTEAD the line number of the start of the function >> [0]PETSC ERROR: is given. >> [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c >> [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c >> [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c >> [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c >> [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c >> [0]PETSC ERROR: --------------------- Error Message >> ------------------------------------ >> [0]PETSC ERROR: Signal received! >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT >> 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 >> [0]PETSC ERROR: See docs/changes/index.html for recent updates. >> [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. >> [0]PETSC ERROR: See docs/index.html for manual pages. >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 >> 14:07:31 2007 >> [0]PETSC ERROR: Libraries linked from >> /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug >> [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 >> [0]PETSC ERROR: Configure options --with-cc-cc >> --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 >> --with-fc=0 --with-shared=0 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown >> file >> Possible error running C/C++ src/snes/examples/tutorials/ex19 with 2 MPI >> processes >> See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html >> [cli_0]: aborting job: >> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 >> [cli_1]: aborting job: >> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 1 >> lid velocity = 0.0016, prandtl # = 1, grashof # = 1 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably >> memory access out of range >> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger >> [0]PETSC ERROR: or see >> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… >> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find >> memory corruption errors >> [0]PETSC ERROR: likely location of problem given in stack below >> [0]PETSC ERROR: --------------------- Stack Frames >> ------------------------------------ >> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, >> [0]PETSC ERROR: INSTEAD the line number of the start of the function >> [0]PETSC ERROR: is given. >> [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c >> [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c >> [0]PETSC ERR[1]PETSC ERROR: >> ------------------------------------------------------------------------ >> [1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably >> memory access out of range >> [1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger >> [1]PETSC ERROR: or see >> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… >> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find >> memory corruption errors >> [1]PETSC ERROR: likely location of problem given in stack below >> [1]PETSC ERROR: --------------------- Stack Frames >> ------------------------------------ >> [1]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, >> [1]PETSC ERROR: INSTEAD the line number of the start of the function >> [1]PETSC ERROR: is given. >> [1]PETSC ERROR: [1] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c >> [1]PETSC ERROR: [1] VecNorm line 148 src/vec/vec/interface/rvector.c >> [1]PETSC ERROR: [1] SNESSolve line 1811 src/snes/interface/snes.OR: [0] >> SNESSolve line 1811 src/snes/interface/snes.c >> [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c >> [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c >> [0]PETSC ERROR: --------------------- Error Message >> ------------------------------------ >> [0]PETSC ERROR: Signal received! >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT >> 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 >> [0]PETSC ERROR: See docs/changes/index.html for recent updates. >> [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. >> [0]PETSC ERROR: See docs/index.html for manual pages. >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 >> 14:07:32 2007 >> [0]PETSC ERROR: Libraries linked from >> /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug >> [0]PETSC ERROR: Configure ruc >> [1]PETSC ERROR: [1] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c >> [1]PETSC ERROR: [1] DMMGSolve line 250 src/snes/utils/damg.c >> [1]PETSC ERROR: --------------------- Error Message >> ------------------------------------ >> [1]PETSC ERROR: Signal received! >> [1]PETSC ERROR: >> ------------------------------------------------------------------------ >> [1]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT >> 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 >> [1]PETSC ERROR: See docs/changes/index.html for recent updates. >> [1]PETSC ERROR: See docs/faq.html for hints about trouble shooting. >> [1]PETSC ERROR: See docs/index.html for manual pages. >> [1]PETSC ERROR: >> ------------------------------------------------------------------------ >> [1]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 >> 14:07:32 2007 >> [1]PETSC ERROR: Libraries linked from >> /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug >> [1]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 >> [1]PETSC ERROR: Confign at Tue May 15 11:05:42 2007 >> [0]PETSC ERROR: Configure options --with-cc-cc >> --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 >> --with-fc=0 --with-shared=0 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown >> file >> ure options --with-cc-cc >> --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 >> --with-fc=0 --with-shared=0 >> [1]PETSC ERROR: >> ------------------------------------------------------------------------ >> [1]PETSC ERROR: User provided function() line 0 in unknown directory unknown >> file >> Possible error running Graphics examples src/snes/examples/tutorials/ex19 1 >> MPI process >> See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html >> [cli_0]: aborting job: >> application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 >> lid velocity = 0.0016, prandtl # = 1, grashof # = 1 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably >> memory access out of range >> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger >> [0]PETSC ERROR: or see >> http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… >> ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find >> memory corruption errors >> [0]PETSC ERROR: likely location of problem given in stack below >> [0]PETSC ERROR: --------------------- Stack Frames >> ------------------------------------ >> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, >> [0]PETSC ERROR: INSTEAD the line number of the start of the function >> [0]PETSC ERROR: is given. >> [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c >> [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c >> [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c >> [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c >> [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c >> [0]PETSC ERROR: --------------------- Error Message >> ------------------------------------ >> [0]PETSC ERROR: Signal received! >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT >> 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 >> [0]PETSC ERROR: See docs/changes/index.html for recent updates. >> [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. >> [0]PETSC ERROR: See docs/index.html for manual pages. >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 >> 14:07:34 2007 >> [0]PETSC ERROR: Libraries linked from >> /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug >> [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 >> [0]PETSC ERROR: Configure options --with-cc-cc >> --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 >> --with-fc=0 --with-shared=0 >> [0]PETSC ERROR: >> ------------------------------------------------------------------------ >> [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown >> file >> Completed test examples >> >> It looks like there is a fatal error in memory operations at the >> PetscFunctionBegin macro. >> >> Regards, >> Adam >> >> >> > >

1 0

Re: Sun Studio Performance Library
by Satish Balay 16 May '07

16 May '07

We have it working on a solaris [sparc] box - so I'm not sure what the problem here is.. You can run this in a debugger to chek where it crashing.. If you have -lsunperf, configure shoul automatically detect it [so no extra option is necessary] Also - looks like -lsunperf requires -lsunmath -lm - so perhaps these need specifying? [petsc-dev(a)mcs.anl.gov is not an appropriate list for such discussions. You can send these issues to petsc-maint(a)mcs.anl.gov. If you wish to discuss thse issues in a public list - then you can use petsc-users(a)mcs.anl.gov list] Satish On Wed, 16 May 2007, Yi-Feng Adam Zhang wrote: > Hi all, > > Does anyone use the latest Sun Studio Performance Library(libsunperf.a) with > PETSc? I just make a compilation but failed in the test stage. > > The configure.py is : > #!/usr/bin/env python > if __name__ == '__main__': > import sys > sys.path.insert(0, '/work/adam/petsc/perf.mpi.suncc.blas.c/config') > import configure > configure_options = ['--with-cc-cc', '--with-shared=0', '--download-mpich=1', > '-PETSC_ARCH=solaris2.10-c-debug', > '--with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so', '--with-fc=0'] > configure.petsc_configure(configure_options) > > > The error message I get after issue "make test": > -bash-3.00# make test > Running test examples to verify correct installation > Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI > processSee > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html > [cli_0]: aborting job: > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 > lid velocity = 0.0016, prandtl # = 1, grashof # = 1 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably > memory access out of range > [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger > [0]PETSC ERROR: or see > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find > memory corruption errors > [0]PETSC ERROR: likely location of problem given in stack below > [0]PETSC ERROR: --------------------- Stack Frames > ------------------------------------ > [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, > [0]PETSC ERROR: INSTEAD the line number of the start of the function > [0]PETSC ERROR: is given. > [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c > [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c > [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c > [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c > [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c > [0]PETSC ERROR: --------------------- Error Message > ------------------------------------ > [0]PETSC ERROR: Signal received! > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT > 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [0]PETSC ERROR: See docs/index.html for manual pages. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 > 14:07:31 2007 > [0]PETSC ERROR: Libraries linked from > /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug > [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 > [0]PETSC ERROR: Configure options --with-cc-cc > --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 > --with-fc=0 --with-shared=0 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown > file > Possible error running C/C++ src/snes/examples/tutorials/ex19 with 2 MPI > processes > See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html > [cli_0]: aborting job: > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 > [cli_1]: aborting job: > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 1 > lid velocity = 0.0016, prandtl # = 1, grashof # = 1 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably > memory access out of range > [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger > [0]PETSC ERROR: or see > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find > memory corruption errors > [0]PETSC ERROR: likely location of problem given in stack below > [0]PETSC ERROR: --------------------- Stack Frames > ------------------------------------ > [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, > [0]PETSC ERROR: INSTEAD the line number of the start of the function > [0]PETSC ERROR: is given. > [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c > [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c > [0]PETSC ERR[1]PETSC ERROR: > ------------------------------------------------------------------------ > [1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably > memory access out of range > [1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger > [1]PETSC ERROR: or see > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find > memory corruption errors > [1]PETSC ERROR: likely location of problem given in stack below > [1]PETSC ERROR: --------------------- Stack Frames > ------------------------------------ > [1]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, > [1]PETSC ERROR: INSTEAD the line number of the start of the function > [1]PETSC ERROR: is given. > [1]PETSC ERROR: [1] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c > [1]PETSC ERROR: [1] VecNorm line 148 src/vec/vec/interface/rvector.c > [1]PETSC ERROR: [1] SNESSolve line 1811 src/snes/interface/snes.OR: [0] > SNESSolve line 1811 src/snes/interface/snes.c > [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c > [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c > [0]PETSC ERROR: --------------------- Error Message > ------------------------------------ > [0]PETSC ERROR: Signal received! > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT > 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [0]PETSC ERROR: See docs/index.html for manual pages. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 > 14:07:32 2007 > [0]PETSC ERROR: Libraries linked from > /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug > [0]PETSC ERROR: Configure ruc > [1]PETSC ERROR: [1] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c > [1]PETSC ERROR: [1] DMMGSolve line 250 src/snes/utils/damg.c > [1]PETSC ERROR: --------------------- Error Message > ------------------------------------ > [1]PETSC ERROR: Signal received! > [1]PETSC ERROR: > ------------------------------------------------------------------------ > [1]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT > 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 > [1]PETSC ERROR: See docs/changes/index.html for recent updates. > [1]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [1]PETSC ERROR: See docs/index.html for manual pages. > [1]PETSC ERROR: > ------------------------------------------------------------------------ > [1]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 > 14:07:32 2007 > [1]PETSC ERROR: Libraries linked from > /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug > [1]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 > [1]PETSC ERROR: Confign at Tue May 15 11:05:42 2007 > [0]PETSC ERROR: Configure options --with-cc-cc > --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 > --with-fc=0 --with-shared=0 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown > file > ure options --with-cc-cc > --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 > --with-fc=0 --with-shared=0 > [1]PETSC ERROR: > ------------------------------------------------------------------------ > [1]PETSC ERROR: User provided function() line 0 in unknown directory unknown > file > Possible error running Graphics examples src/snes/examples/tutorials/ex19 1 > MPI process > See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html > [cli_0]: aborting job: > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 > lid velocity = 0.0016, prandtl # = 1, grashof # = 1 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably > memory access out of range > [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger > [0]PETSC ERROR: or see > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find > memory corruption errors > [0]PETSC ERROR: likely location of problem given in stack below > [0]PETSC ERROR: --------------------- Stack Frames > ------------------------------------ > [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, > [0]PETSC ERROR: INSTEAD the line number of the start of the function > [0]PETSC ERROR: is given. > [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c > [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c > [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c > [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c > [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c > [0]PETSC ERROR: --------------------- Error Message > ------------------------------------ > [0]PETSC ERROR: Signal received! > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT > 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [0]PETSC ERROR: See docs/index.html for manual pages. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 > 14:07:34 2007 > [0]PETSC ERROR: Libraries linked from > /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug > [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 > [0]PETSC ERROR: Configure options --with-cc-cc > --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 > --with-fc=0 --with-shared=0 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown > file > Completed test examples > > It looks like there is a fatal error in memory operations at the > PetscFunctionBegin macro. > > Regards, > Adam > >

1 0

Sun Studio Performance Library
by Yi-Feng Adam Zhang 16 May '07

16 May '07

Hi all, Does anyone use the latest Sun Studio Performance Library(libsunperf.a) with PETSc? I just make a compilation but failed in the test stage. The configure.py is : #!/usr/bin/env python if __name__ == '__main__': import sys sys.path.insert(0, '/work/adam/petsc/perf.mpi.suncc.blas.c/config') import configure configure_options = ['--with-cc-cc', '--with-shared=0', '--download-mpich=1', '-PETSC_ARCH=solaris2.10-c-debug', '--with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so', '--with-fc=0'] configure.petsc_configure(configure_options) The error message I get after issue "make test": -bash-3.00# make test Running test examples to verify correct installation Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI processSee http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html [cli_0]: aborting job: application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 lid velocity = 0.0016, prandtl # = 1, grashof # = 1 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find memory corruption errors [0]PETSC ERROR: likely location of problem given in stack below [0]PETSC ERROR: --------------------- Stack Frames ------------------------------------ [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, [0]PETSC ERROR: INSTEAD the line number of the start of the function [0]PETSC ERROR: is given. [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 14:07:31 2007 [0]PETSC ERROR: Libraries linked from /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 [0]PETSC ERROR: Configure options --with-cc-cc --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 --with-fc=0 --with-shared=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Possible error running C/C++ src/snes/examples/tutorials/ex19 with 2 MPI processes See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html [cli_0]: aborting job: application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 [cli_1]: aborting job: application called MPI_Abort(MPI_COMM_WORLD, 59) - process 1 lid velocity = 0.0016, prandtl # = 1, grashof # = 1 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find memory corruption errors [0]PETSC ERROR: likely location of problem given in stack below [0]PETSC ERROR: --------------------- Stack Frames ------------------------------------ [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, [0]PETSC ERROR: INSTEAD the line number of the start of the function [0]PETSC ERROR: is given. [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c [0]PETSC ERR[1]PETSC ERROR: ------------------------------------------------------------------------ [1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [1]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find memory corruption errors [1]PETSC ERROR: likely location of problem given in stack below [1]PETSC ERROR: --------------------- Stack Frames ------------------------------------ [1]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, [1]PETSC ERROR: INSTEAD the line number of the start of the function [1]PETSC ERROR: is given. [1]PETSC ERROR: [1] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c [1]PETSC ERROR: [1] VecNorm line 148 src/vec/vec/interface/rvector.c [1]PETSC ERROR: [1] SNESSolve line 1811 src/snes/interface/snes.OR: [0] SNESSolve line 1811 src/snes/interface/snes.c [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 14:07:32 2007 [0]PETSC ERROR: Libraries linked from /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug [0]PETSC ERROR: Configure ruc [1]PETSC ERROR: [1] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c [1]PETSC ERROR: [1] DMMGSolve line 250 src/snes/utils/damg.c [1]PETSC ERROR: --------------------- Error Message ------------------------------------ [1]PETSC ERROR: Signal received! [1]PETSC ERROR: ------------------------------------------------------------------------ [1]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 [1]PETSC ERROR: See docs/changes/index.html for recent updates. [1]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [1]PETSC ERROR: See docs/index.html for manual pages. [1]PETSC ERROR: ------------------------------------------------------------------------ [1]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 14:07:32 2007 [1]PETSC ERROR: Libraries linked from /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug [1]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 [1]PETSC ERROR: Confign at Tue May 15 11:05:42 2007 [0]PETSC ERROR: Configure options --with-cc-cc --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 --with-fc=0 --with-shared=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file ure options --with-cc-cc --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 --with-fc=0 --with-shared=0 [1]PETSC ERROR: ------------------------------------------------------------------------ [1]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Possible error running Graphics examples src/snes/examples/tutorials/ex19 1 MPI process See http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html [cli_0]: aborting job: application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 lid velocity = 0.0016, prandtl # = 1, grashof # = 1 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Si… ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to find memory corruption errors [0]PETSC ERROR: likely location of problem given in stack below [0]PETSC ERROR: --------------------- Stack Frames ------------------------------------ [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available, [0]PETSC ERROR: INSTEAD the line number of the start of the function [0]PETSC ERROR: is given. [0]PETSC ERROR: [0] VecNorm_MPI line 57 src/vec/vec/impls/mpi/pvec2.c [0]PETSC ERROR: [0] VecNorm line 148 src/vec/vec/interface/rvector.c [0]PETSC ERROR: [0] SNESSolve line 1811 src/snes/interface/snes.c [0]PETSC ERROR: [0] DMMGSolveSNES line 402 src/snes/utils/damgsnes.c [0]PETSC ERROR: [0] DMMGSolve line 250 src/snes/utils/damg.c [0]PETSC ERROR: --------------------- Error Message ------------------------------------ [0]PETSC ERROR: Signal received! [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 10, Wed Mar 28 19:13:22 CDT 2007 HG revision: d7298c71db7f5e767f359ae35d33cab3bed44428 [0]PETSC ERROR: See docs/changes/index.html for recent updates. [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. [0]PETSC ERROR: See docs/index.html for manual pages. [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: ./ex19 on a solaris2. named newjersey by root Wed May 16 14:07:34 2007 [0]PETSC ERROR: Libraries linked from /work/adam/petsc/perf.mpi.suncc.blas.c/lib/solaris2.10-c-debug [0]PETSC ERROR: Configure run at Tue May 15 11:05:42 2007 [0]PETSC ERROR: Configure options --with-cc-cc --with-blas-lapack-lib=/opt/SUNWspro/lib/libsunperf.so --download-mpich=1 --with-fc=0 --with-shared=0 [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown file Completed test examples It looks like there is a fatal error in memory operations at the PetscFunctionBegin macro. Regards, Adam

1 0

Re: Compiling on Solaris 10 for X86
by Yi-Feng Adam Zhang 11 May '07

11 May '07

Hi Satish, Yes. I just finished the compilation, including BLAS, LAPACK and MPICH and the test stage (bundled in the makefile) with GCC and Sun Studio. PETSc performs great. The code is very wonderful, cross multi-platform indeed. I hope I can maintain a stable Solaris release for PETSc. However my team is very new. Lots of things are still under determination. I will update you via this petsc-dev alias later if I have a firm plan. Thank you! Regards, Adam Satish Balay wrote: > On Fri, 11 May 2007, Yi-Feng Adam Zhang wrote: > > >> I am a Software Engineer, working for Sun Microsystems. My team is >> called Open Source Team. Our intend or goal is to make some >> significant invest on Open Source Community to support them to make >> their software or solution available on Solaris and Sun Grid. Both >> of them are open sourced now: www.opensolaris.org, >> https://sungrid.dev.java.net/ and http://gridengine.sunsource.net/ >> PETSc is a well known with high-profile community in Scientific >> Computing area. I'd like to port PETSc to Solaris OS 10 for X86 >> Platform and make it available on Sun Grid Compute Utility which is >> available from http://www.network.com . If everything is OK both on >> technical side and license side. >> > > http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/copyright.html > I don't think there is an issue with redistribution from the license > side. > > And PETSc compiles on may platforms with different types of compilers > [including sparc-solaris, sun compilers on linux etc..], so I don't > see any technical issues with here. > > > >> I'd like to release a Solaris Package on the Internet, Maybe PETSc >> website, https://sungrid.dev.java.net/ or other 3rd party >> website. So the developers including Solaris developers or Sun Grid >> Developers can use or adopt the PETSc with a already-built Solaris >> Package. >> > > PETSc keeps evolving with patch updates and new releases every so > often. Do you see the work of providing "PETSc for opensolaris > binaries" as a continues package maintainance effort? [or just a one > time port..] > > Its just that one time ports have been attempted before - and they get > out-of-date before they were even released [so they were not very > useful] > > >> BTW, I find I can't subscribe or use another alias: >> petsc-maint(a)mcs.anl.gov which is mainly for installation & >> compilation questioning. Is this alias still working? >> > > This address is still valid and used for all correspondence to petsc > developers - thats not appropriate/relavent to public mailing lists. > > Satish > >

1 0

Re: Compiling on Solaris 10 for X86
by Satish Balay 10 May '07

10 May '07

On Fri, 11 May 2007, Yi-Feng Adam Zhang wrote: > I am a Software Engineer, working for Sun Microsystems. My team is > called Open Source Team. Our intend or goal is to make some > significant invest on Open Source Community to support them to make > their software or solution available on Solaris and Sun Grid. Both > of them are open sourced now: www.opensolaris.org, > https://sungrid.dev.java.net/ and http://gridengine.sunsource.net/ > PETSc is a well known with high-profile community in Scientific > Computing area. I'd like to port PETSc to Solaris OS 10 for X86 > Platform and make it available on Sun Grid Compute Utility which is > available from http://www.network.com . If everything is OK both on > technical side and license side. http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/copyright.html I don't think there is an issue with redistribution from the license side. And PETSc compiles on may platforms with different types of compilers [including sparc-solaris, sun compilers on linux etc..], so I don't see any technical issues with here. > I'd like to release a Solaris Package on the Internet, Maybe PETSc > website, https://sungrid.dev.java.net/ or other 3rd party > website. So the developers including Solaris developers or Sun Grid > Developers can use or adopt the PETSc with a already-built Solaris > Package. PETSc keeps evolving with patch updates and new releases every so often. Do you see the work of providing "PETSc for opensolaris binaries" as a continues package maintainance effort? [or just a one time port..] Its just that one time ports have been attempted before - and they get out-of-date before they were even released [so they were not very useful] > BTW, I find I can't subscribe or use another alias: > petsc-maint(a)mcs.anl.gov which is mainly for installation & > compilation questioning. Is this alias still working? This address is still valid and used for all correspondence to petsc developers - thats not appropriate/relavent to public mailing lists. Satish

1 0

Re: Compiling on Solaris 10 for X86
by Yi-Feng Adam Zhang 10 May '07

10 May '07

Hi Matt, I am a Software Engineer, working for Sun Microsystems. My team is called Open Source Team. Our intend or goal is to make some significant invest on Open Source Community to support them to make their software or solution available on Solaris and Sun Grid. Both of them are open sourced now: www.opensolaris.org, https://sungrid.dev.java.net/ and http://gridengine.sunsource.net/ PETSc is a well known with high-profile community in Scientific Computing area. I'd like to port PETSc to Solaris OS 10 for X86 Platform and make it available on Sun Grid Compute Utility which is available from http://www.network.com . If everything is OK both on technical side and license side, I'd like to release a Solaris Package on the Internet, Maybe PETSc website, https://sungrid.dev.java.net/ or other 3rd party website. So the developers including Solaris developers or Sun Grid Developers can use or adopt the PETSc with a already-built Solaris Package. BTW, I find I can't subscribe or use another alias: petsc-maint(a)mcs.anl.gov which is mainly for installation & compilation questioning. Is this alias still working? Regards, Adam Matthew Knepley wrote: > On 5/10/07, Adam Zhang <Adam.Zhang(a)sun.com> wrote: >> Thank you for input. I will try to use gmake later. >> >> If this compilation is ok. can I release this as a Solaris package on >> the internet? > > I guess. What is it for? > > Thanks, > > Matt > >> Regards, >> Adam >> >> >> Matthew Knepley wrote: >> > Nothing is wrong with the PETSc build or libraries. However, your make >> > (probably not gmake) has a problem with the make rule that cleans up >> > files >> > in bmake/common/rules:359. You can just ignore it (or tell us what is >> > wrong). >> > >> > Thanks, >> > >> > Matt >> > >> > On 5/10/07, Yi-Feng Adam Zhang <Adam.Zhang(a)sun.com> wrote: >> >> Hi all, >> >> >> >> Recently I am compiling the PETSc 2.3.2 -P10 on Solaris 10 for X86 >> with >> >> GCC and Sun's f90. >> >> Here is the command I give to configure.py: >> >> ./config/configure.py --download-f-blas-lapack=1 --with-mpi=0 >> >> >> >> Yes. I don't use the MPI intendedly. Because I want to make sure >> every >> >> thing is ok before using MPI. >> >> When I input the command "make all", every thing looks fine. >> >> But when I try to use "make test" to verify, I get the following >> error: >> >> ---------------------------------------------- >> >> -bash-3.00# more test_log_solaris2.10-c-debug >> >> Running test examples to verify correct installation >> >> C/C++ example src/snes/examples/tutorials/ex19 run successfully >> with 1 >> >> MPI process >> >> Graphics example src/snes/examples/tutorials/ex19 run successfully >> with >> >> 1 MPI process >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex19.exe; then /usr/bin/rm -f ex19.exe; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex19.ilk; then /usr/bin/rm -f ex19.ilk; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex19.pdb; then /usr/bin/rm -f ex19.pdb; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex19.tds; then /usr/bin/rm -f ex19.tds; fi >> >> Fortran example src/snes/examples/tutorials/ex5f run successfully >> with 1 >> >> MPI process >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex5f.exe; then /usr/bin/rm -f ex5f.exe; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex5f.ilk; then /usr/bin/rm -f ex5f.ilk; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex5f.pdb; then /usr/bin/rm -f ex5f.pdb; fi >> >> sh: test: argument expected >> >> *** Error code 1 (ignored) >> >> The following command caused the error: >> >> if test -e ex5f.tds; then /usr/bin/rm -f ex5f.tds; fi >> >> Completed test examples >> >> ----------------------------------------------- >> >> >> >> Does anyone have any suggestion? Thanks in advance! >> >> >> >> Regards, >> >> Adam >> >> >> >> >> > >> > >> >> > >

1 0

Re: Compiling on Solaris 10 for X86
by Yi-Feng Adam Zhang 10 May '07

10 May '07

Hi Satish, You are right. /usr/bin/sh doesn't support "test" with "-e" option. Thank you very much! Regards, Adam Satish Balay wrote: >> if test -e ex19.exe; then /usr/bin/rm -f ex19.exe; fi >> > > Looks like this is an issue with /bin/sh on solaris [and with test > command supported by it]. Our solaris build appears to pick up > /usr/xpg4/bin/sh and the build works fine with it. > > Satish > > > ------ > > > > On Thu, 10 May 2007, Matthew Knepley wrote: > > >> Nothing is wrong with the PETSc build or libraries. However, your make >> (probably not gmake) has a problem with the make rule that cleans up files >> in bmake/common/rules:359. You can just ignore it (or tell us what is wrong). >> >> Thanks, >> >> Matt >> >> On 5/10/07, Yi-Feng Adam Zhang <Adam.Zhang(a)sun.com> wrote: >> >>> Hi all, >>> >>> Recently I am compiling the PETSc 2.3.2 -P10 on Solaris 10 for X86 with >>> GCC and Sun's f90. >>> Here is the command I give to configure.py: >>> ./config/configure.py --download-f-blas-lapack=1 --with-mpi=0 >>> >>> Yes. I don't use the MPI intendedly. Because I want to make sure every >>> thing is ok before using MPI. >>> When I input the command "make all", every thing looks fine. >>> But when I try to use "make test" to verify, I get the following error: >>> ---------------------------------------------- >>> -bash-3.00# more test_log_solaris2.10-c-debug >>> Running test examples to verify correct installation >>> C/C++ example src/snes/examples/tutorials/ex19 run successfully with 1 >>> MPI process >>> Graphics example src/snes/examples/tutorials/ex19 run successfully with >>> 1 MPI process >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex19.exe; then /usr/bin/rm -f ex19.exe; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex19.ilk; then /usr/bin/rm -f ex19.ilk; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex19.pdb; then /usr/bin/rm -f ex19.pdb; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex19.tds; then /usr/bin/rm -f ex19.tds; fi >>> Fortran example src/snes/examples/tutorials/ex5f run successfully with 1 >>> MPI process >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex5f.exe; then /usr/bin/rm -f ex5f.exe; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex5f.ilk; then /usr/bin/rm -f ex5f.ilk; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex5f.pdb; then /usr/bin/rm -f ex5f.pdb; fi >>> sh: test: argument expected >>> *** Error code 1 (ignored) >>> The following command caused the error: >>> if test -e ex5f.tds; then /usr/bin/rm -f ex5f.tds; fi >>> Completed test examples >>> ----------------------------------------------- >>> >>> Does anyone have any suggestion? Thanks in advance! >>> >>> Regards, >>> Adam >>> >>> >>> >> >> > >

1 0

Re: Compiling on Solaris 10 for X86
by Satish Balay 10 May '07

10 May '07

> if test -e ex19.exe; then /usr/bin/rm -f ex19.exe; fi Looks like this is an issue with /bin/sh on solaris [and with test command supported by it]. Our solaris build appears to pick up /usr/xpg4/bin/sh and the build works fine with it. Satish ------ On Thu, 10 May 2007, Matthew Knepley wrote: > Nothing is wrong with the PETSc build or libraries. However, your make > (probably not gmake) has a problem with the make rule that cleans up files > in bmake/common/rules:359. You can just ignore it (or tell us what is wrong). > > Thanks, > > Matt > > On 5/10/07, Yi-Feng Adam Zhang <Adam.Zhang(a)sun.com> wrote: > > Hi all, > > > > Recently I am compiling the PETSc 2.3.2 -P10 on Solaris 10 for X86 with > > GCC and Sun's f90. > > Here is the command I give to configure.py: > > ./config/configure.py --download-f-blas-lapack=1 --with-mpi=0 > > > > Yes. I don't use the MPI intendedly. Because I want to make sure every > > thing is ok before using MPI. > > When I input the command "make all", every thing looks fine. > > But when I try to use "make test" to verify, I get the following error: > > ---------------------------------------------- > > -bash-3.00# more test_log_solaris2.10-c-debug > > Running test examples to verify correct installation > > C/C++ example src/snes/examples/tutorials/ex19 run successfully with 1 > > MPI process > > Graphics example src/snes/examples/tutorials/ex19 run successfully with > > 1 MPI process > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex19.exe; then /usr/bin/rm -f ex19.exe; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex19.ilk; then /usr/bin/rm -f ex19.ilk; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex19.pdb; then /usr/bin/rm -f ex19.pdb; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex19.tds; then /usr/bin/rm -f ex19.tds; fi > > Fortran example src/snes/examples/tutorials/ex5f run successfully with 1 > > MPI process > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex5f.exe; then /usr/bin/rm -f ex5f.exe; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex5f.ilk; then /usr/bin/rm -f ex5f.ilk; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex5f.pdb; then /usr/bin/rm -f ex5f.pdb; fi > > sh: test: argument expected > > *** Error code 1 (ignored) > > The following command caused the error: > > if test -e ex5f.tds; then /usr/bin/rm -f ex5f.tds; fi > > Completed test examples > > ----------------------------------------------- > > > > Does anyone have any suggestion? Thanks in advance! > > > > Regards, > > Adam > > > > > > >

1 0