On Fri, 4 Dec 2009, Kirk, Benjamin (JSC-EG311) wrote:
> We do this implictliy, I believe. We only initialize petsc if we > initialize mpi, right? So if the user initializes petsc externally, > mpi will be enabled and we will not initialize anything. We only initialize PETSc if we're compiled with MPI, but we did initialize PETSc ourselves regardless. That's good for the case where we're called from a user code that initializes MPI regardless but doesn't initialize PETSc (like QUESO, which first got me looking at the problem), but we may get called from user codes that handle both. Anyway, I've updated libmesh.C, and I think we're correct now. The only obvious remaining bug is that LibMeshInit isn't thread-safe, but if anyone wants to create two LibMeshInit objects in two different threads then the obvious workaround is "don't do that!" --- Roy ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
