From: Kirk, Benjamin \(JSC-EG\) <benjamin.kirk-1@na...> - 2006-06-19 15:23:40
Please post the output of 'make echo'
Libmesh digs into the PETSc configuration to determine where the MPI =
libraries are installed. This usually works well but seems like it is =
failing in your case.
The symptom, as you have found, is that the MPI libraries are not making =
it onto the link line.=20
From: libmesh-devel-bounces@... =
[mailto:libmesh-devel-bounces@...] On Behalf Of Tim =
Sent: Friday, June 16, 2006 1:54 AM
Subject: [Libmesh-devel] Question about linkling libmesh with PETSc
Dear libMesh developers,
I'm curruently trying to get familiar with libMesh but encouter a =
linking problem when using PETSc. The libMesh library itself compiles =
and links perfectly, but whenever I try to build one of the examples, I =
get error messages like this:
Compiling C++ (in optimized mode) ex0.C...
In function `tecini':
: warning: the use of `mktemp' is dangerous, better use `mkstemp'
ex0.i686-pc-linux-gnu.opt.o(.text+0x6d9): In function `main':
: undefined reference to `MPI_Abort'
I do not mean the warning about mktemp but the error due to the =
undefined reference. There are in fact lots of undefined references.
I can avoid the problem by specifying "-lmpich" manually in the makefile =
but I wonder why this is necessary.
I would be glad if you could help me.
Dr. Tim Kroeger
CeVis -- Center of Complex Systems and Visualization University of =
Universitaetsallee 29 (Office 3.13) tim@...
D-28359 Bremen Phone +49-421-218-7710
Germany Fax +49-421-218-4236
Libmesh-devel mailing list
please find attached the output of 'make echo'.
Where would I have to specify the MPI libraries globally? Currently,
I'm just adding "-lmpich" in the Makefile of each of the examples
individually, which works fine. In particular, I do not need to
specify any path. Setting MPI_LIB=-lmpich in Make.common, however,
does not work.
Thank you very much for your help.
Get latest updates about Open Source Projects, Conferences and News.