Thanks for you reply. the libmesh_LIBS output has references to mpi, -lmpich and -lmpichf90. Would it help to post the whole output?
Jens On 04/16/2012 10:03 AM, John Peterson wrote: > On Sun, Apr 15, 2012 at 2:11 PM, Jens Lohne Eftang<[email protected]> wrote: >> Dear all, >> >> I want to use the mumps direct sparse solvers. I've (seemingly) >> successfully configured and compiled petsc with mumps, and then >> configured and compiled libmesh. Compiling programs works fine, but when >> I try to run my program with >> >> ./program -pc_factor_mat_solver_package mumps >> >> I get the run time error >> >> symbol lookup error: >> /home/eftang/fem_software/petsc-3.2-p5/arch-linux2-c-opt/lib/libpetsc.so: >> undefined >> symbol: mpi_bcast_ >> >> when my program attempts the solve. > It almost seems like the location of your MPI libraries is not in > LD_LIBRARY_PATH and it has not been set with linker options, e.g. > > -Wl,-rpath,/opt/packages/mpich2/mpich2-1.3.2/gnu-opt/lib > > Could you check the libmesh_LIBS output of 'make echo' for any > references to MPI? > > Libmesh usually gets its MPI flags from PETSc, specifically the > petscconf/petscvariables file, so you should check there as well to > see if those are correct... > ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
