On Wed, Apr 18, 2012 at 1:32 PM, John Peterson <[email protected]> wrote:
> On Wed, Apr 18, 2012 at 12:05 PM, Dmitry Karpeev <[email protected]> > wrote: > > On Wed, Apr 18, 2012 at 11:47 AM, Jens Lohne Eftang <[email protected]> > > wrote: > >> > >> petsch make test runs ex19 with 1 and 2 mpi processes and ex5f with 1 > mpi > >> process sucessfully. > > > > I'm guessing the problem is with the way libMesh uses PETSc's compilers. > > I'm not sure exactly how libMesh deals with it when PETSc doesn't define > a > > C++ compiler. > > > Perhaps then an mpicxx from another mpi install ends up being used? > > Maybe John can answer that. > > I suppose it's possible if he has multiple MPI installations on his system? > > Libmesh uses the first mpicxx it finds in your path unless you specify > I was under the impression that libMesh tried to use the compilers that PETSc configured (provided libMesh was itself configured with PETSc). > > CXX=/path/to/some/mpi/mpicxx ./configure ... > Okay, then I think the problem is that PETSc is linked against mpi from /home/eftang/fem_software/mpich2-install, while the mpicxx that libMesh finds links the executable against a different mpich. I would recommend reconfiguring PETSc using --with-clanguage=C++ and making sure that libMesh uses the same mpicxx as PETSc. Dmitry. > > -- > John > ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
