On Fri, 8 Apr 2016, Harriet Li wrote: > I think the problem might have been that I followed the standard > petsc installation and used --download-mpich, which seemed to have > installed mpich somewhere that petsc would use it but that wouldn't > show up with 'whereis'.
Oh, certainly! That would break it. You'd be linking with mpich (because we autodetect MPI from PETSc to try and reduce incompatibilities there) but be running with openmpi (because that's what bash will find when you execute mpirun). > I ended up getting Example 4 to work by specifying --with-mpi-dir in > both my petsc and libmesh configurations and recompiling. Good to hear; thanks for letting everyone know the resolution. --- Roy ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
