This sounds like a canonical problem of mixing multiple MPI libraries
(e.g., trying to run a LAM-compiled executable against MPICH's
libmpi.so).
Ensure that you are compiling your application against the same MPI
library that you are running it with. If you're using LAM's wrapper
compilers (e.g., "mpicc"), all the links should be setup properly,
although there are a few cases where things can still go wrong:
- if you compiled LAM statically (the default) and installed it to a
$prefix where a shared library version of libmpi exists, when you mpicc,
the linker will prefer the .so instead of the .a
- if you compiled LAM dynamically and compiled your application with
LAM's mpicc but then ran it with LD_LIBRARY_PATH pointing to some other
MPI implementation's library path
I'm guessing that one of the two scenarios listed above is happening.
________________________________
From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]]
On Behalf Of YoungHui Amend
Sent: Thursday, June 15, 2006 6:44 PM
To: General LAM/MPI mailing list
Subject: LAM: libmpi.so: undefined symbol:
lam_ssi_base_module_compare
Hi,
I'm running LAM/MPI 7.1.2 on amd64_linux24 machine and getting
the following error:
libmpi.so: undefined symbol: lam_ssi_base_module_compare
Where is this defined and why was it not linked in? What do I
need to do?
Thank You,
YoungHui
|
