>>>> #if LAM_WANT_MPI2CPP & !LAM_BUILDING >>>> #include <mpicxx.h> >>>> #endif >>>> >>>> So I tried adding >>>> >>>> libmesh_CXXFLAGS += -ULAM_WANT_MPI2CPP >>>> >>>> to my Make.common file, although I am not sure whether this is correct >>>> and where LAM_WANT_MPI2CPP actually has been defined. I helps >>>> partially because I now get different error messages: > > I now found a way that works. It consists of adding the following two > lines to Make.common: > > > libmesh_CXXFLAGS += -ULAM_WANT_MPI2CPP > libmesh_LDFLAGS += -L/usr/local/lam-mpi/lib -llammpi++ > > > Since I am not familiar with libMesh's build system, perhaps somebody > else can convert that to a version that does not depend on > installation paths and then commit it to the svn head so that other > users can benefit from it.
>From your petscconf file it seems you built petsc with mpicc and friends, so libMesh cannot "snoop" the MPI configuration. Can you try ./configure --with-cc=mpicc --with-cxx=mpicxx --with-f77=mpif77 ... (or whatever mpi compiler wrappers LAM uses) and give it a shot? The MPI compiler wrappers should find the libraries directly. The -ULAM_WANT_MPI2CPP may or may not still be necessary. -Ben ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
