Dear Roy, On Tue, 8 Apr 2008, Roy Stogner wrote:
>>>> libmesh_CXXFLAGS += -ULAM_WANT_MPI2CPP >>>> libmesh_LDFLAGS += -L/usr/local/lam-mpi/lib -llammpi++ >>> >>> Was the -L/usr/local/lam-mpi/lib necessary? >> >> Yes, although I have no idea why. > > Hmm... it looks like we use PETSc's PACKAGES_LIBS variable when > linking, but we don't use their *_LINKER_LIBS variables. I'm not sure > whether that's PETSc's problem or ours, since they've changed their > config file and variable names repeatedly... But even if we used > PCC_LINKER_LIBS, that still wouldn't duplicate your manual options, > since your PETSc version appears to be built against the C MPI API, > not the "C++"* API; there's no lammpi++ library in there. It might > work anyway, though, since we don't need (or want, for that matter) > the "C++" API either. > > Can you try turning off the MPI2CPP support and manually adding the > LDFLAGS "-L/usr/local/lam-mpi -llammpio -llamf77mpi -llam" instead? Can you please explain a little bit more what you mean by "turning off the MPI2CPP support"? I will then try that tomorrow morning an let you know. Best Regards, Tim -- Dr. Tim Kroeger Phone +49-421-218-7710 [EMAIL PROTECTED], [EMAIL PROTECTED] Fax +49-421-218-4236 MeVis Research GmbH, Universitaetsallee 29, 28359 Bremen, Germany Amtsgericht Bremen HRB 16222 Geschaeftsfuehrer: Prof. Dr. H.-O. Peitgen ------------------------------------------------------------------------- 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
