Hmm, I think I’ll do option 1). I’m more familiar with PETSc/SLEPc than libmesh, so I think that it’ll be simpler to stick to the master branch. Thanks for the indications!
> On 01 Jul 2015, at 16:19, John Peterson <[email protected]> wrote: > > > > On Wed, Jul 1, 2015 at 3:37 AM, Thiago Milanetto Schlittler > <[email protected]> wrote: > Thanks! This seems to do the trick, at least for the installation. The “make” > and “make install” steps work with no problems, but I’m getting an error > during the “make check” step. The failed test output is given below. Should I > be worried by it? > > *************************************************************** > * Running Example miscellaneous_ex3: > * example-dbg -r 3 -o FIRST > *************************************************************** > > [0]PETSC ERROR: --------------------- Error Message > -------------------------------------------------------------- > [0]PETSC ERROR: Object is in wrong state > [0]PETSC ERROR: Vec is locked read only, argument # 1 > [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html for > trouble shooting. > [0]PETSC ERROR: Petsc Release Version 3.6.0, Jun, 09, 2015 > [0]PETSC ERROR: > /Users/breubreubreu/Execs/libmesh/examples/miscellaneous/miscellaneous_ex3/.libs/example-dbg > on a arch-darwin-c-debug named dhcp-103-99.wifi-auth.ecp.fr by breubreubreu > Wed Jul 1 11:27:41 2015 > [0]PETSC ERROR: Configure options --with-cc=mpicc --with-cxx=mpicxx > --with-fc=mpif90 > [0]PETSC ERROR: #1 VecGetArray() line 1646 in > /Users/breubreubreu/Execs/petsc-3.6.0/src/vec/vec/interface/rvector.c > [0]PETSC ERROR: #2 VecAssemblyEnd_MPI() line 1045 in > /Users/breubreubreu/Execs/petsc-3.6.0/src/vec/vec/impls/mpi/pdvec.c > [0]PETSC ERROR: #3 VecAssemblyEnd() line 188 in > /Users/breubreubreu/Execs/petsc-3.6.0/src/vec/vec/interface/vector.c > [0]PETSC ERROR: #4 close() line 952 in ./include/libmesh/petsc_vector.h > -------------------------------------------------------------------------- > > This means that you compiled PETSc 3.6.0 with debugging enabled, which is > stricter about the times when you can actually modify the contents of > vectors... > > libMesh has been partially updated to support this (see the debug_petsc > branch), but there are still some kinks to be worked out. So you have at > least two options: > > 1.) Use a PETSc that has been configured with --with-debugging=0. PETSc is > pretty easy to build from source if you've never tried it. > 2.) Use the debug_petsc branch for the time being. This approach may be > easier/faster than rebuilding PETSc if you are familiar with git. > > -- > John ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
