On Sep 9, 2004, at 2:42 PM, Peter Kjellstroem wrote:
>> MPI.o(.text+0xcc2): undefined reference to `lam_strncpy'
>
> I saw that you fixed it with mpicc and friends, but just to clear up
> the
> original problem:
>
> libmpi needs lam_strncpy which is in liblam which is _before_ libmpi in
> this case... just pust -llam after all the other lam related libs,
> right?
Ah -- yes. I missed this in the original message. libmpi definitely
has a dependency on liblam, not the other way around. Thanks.
But as always, the LAM Team *STRONGLY* recommends using mpicc and
friends rather than listing the libraries (and whatnot) manually. This
is because different versions (and different installations) of LAM may
require different flags. mpicc has always done the Right Thing for LAM
-- there are very, very few cases where you can't use mpicc (most of
them are political, not technical ;-) ).
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
