On Thu, 7 Apr 2016, Harriet Li wrote: > The only MPI's I could find are: > > $ whereis mpirun > mpirun: /usr/bin/mpirun.openmpi /usr/bin/mpirun /usr/bin/X11/mpirun.openmpi > /usr/bin/X11/mpirun /usr/share/man/man1/mpirun.1.gz > > $ whereis mpicxx > mpicxx: /usr/bin/mpicxx /usr/bin/mpicxx.openmpi /usr/bin/X11/mpicxx > /usr/bin/X11/mpicxx.openmpi /usr/share/man/man1/mpicxx.1.gz > > $ whereis mpicc > mpicc: /usr/bin/mpicc /usr/bin/mpicc.openmpi /usr/bin/X11/mpicc > /usr/bin/X11/mpicc.openmpi /usr/share/man/man1/mpicc.1.gz > > Not sure if this counts as multiple MPIs...
Me neither. They could be symlinks to the same target. What does "ls -l $(whereis mpirun)" say? How about "md5sum $(whereis mpirun)"? It's also important that no multiple versions got in during compiling or linking. To check for the most glaring errors: If you're using libtool to build yourapplication-devel then in the build directory you'd run "ldd .libs/yourapplication-devel | grep mpi"; if you're in the install directory or not using libtool you'd just run "ldd yourapplication-devel | grep mpi" What distribution are you using? This looks like the Debian/Ubuntu/etc way of setting up mpich-vs-openmpi; is it possible that you previously compiled with mpich but didn't start running until changing the libraries underneath you? What happens if you build and run http://mpitutorial.com/tutorials/mpi-hello-world/ Try it first by hand, then with $(libmesh-config --cxx) etc. --- Roy ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
