It is likely just a matter of using the mpiexec in PATH (e.g. /usr/bin) instead of /home/yujie/codes/mpich2/bin/mpiexec. Note that either mpicc links with RPATH (MPICH2), or mpiexec sets up the environment so that the correct libraries are found (Open MPI; LD_LIBRARY_PATH may change in which case mpiexec -n 1 ./app works, but ./app doesn't) so shared libs should work correctly even if you don't modify LD_LIBRARY_PATH by hand. IIRC, libmesh always links with RPATH (and PETSc certainly does).
Jed ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users