On Tue, 16 Mar 2010 15:50:50 -0500 (CDT), Roy Stogner <[email protected]> wrote: > > On Tue, 16 Mar 2010, Edouard Oudet wrote: > > > One last question : do you think it would be a hard task to adapt the code > > to options --enable-petsc --disable-mpi ? > > Not sure. It wouldn't touch most of the library, but there's > definitely fixes needed in configure.in, libmesh_common.h libmesh.C, > and petsc.m4. Possibly extensively in petsc_*.C and petsc_*.h as > well. I don't even know what CHKERRABORT is supposed to do if PETSc > is configured --with-mpi=0 and MPI_Abort isn't available.
As you probably know, --with-mpi=0 just means that PETSc uses a mock implementation (mpiuni, a slightly incomplete serial implementation). In this case, MPI_Abort() is still defined and just calls abort(). Jed ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
