On Thu, 9 Sep 2004, Peter Schmid wrote:
> All,
>
> I have some software developers that I support. They have a large
> application that they have been running fine with MPICH (1.2.3-1.2.5) with
> no problems. They now need to create a build with LAM. I have d/l lam
> 7.0.6 and compiled fine now on IA64. When compiling and linking their
> appliciation against LAM I get the following:
>
> /software/lam_7.0.6/linux/intel/7.1_64/lib/libmpi.a(MPI.o): In function
> `lam_F2C_string':
> 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?
/Peter
> /software/lam_7.0.6/linux/intel/7.1_64/lib/libmpi.a(MPI.o): In function
> `lam_C2F_string':
> MPI.o(.text+0xde2): undefined reference to `lam_strncpy'
> /software/lam_7.0.6/linux/intel/7.1_64/lib/libmpi.a(MPI.o): In function
> `lam_F2C_argv':
> MPI.o(.text+0xf12): undefined reference to `argvfree'
> MPI.o(.text+0xf82): undefined reference to `argvadd'
> MPI.o(.text+0xfd2): undefined reference to `argvfree'
>
>
> My link line for MPICH vs LAM is as follows:
> # MPICH LINE
> #MPILIB = -L$(MPIDIR)/lib -lmpichf90 -lmpich -lPEPCF90
> # LAM LINE
> MPILIB = -L$(MPIDIR)/lib -llamf77mpi -llam -lmpi -llammpi++ -llammpio
>
> Anyone there familar with MPICH vs LAM.. and can give me some pointers to
> pass onto my developers?
>
> Thanks,
>
> Pete.
>
--
------------------------------------------------------------
Peter Kjellstroem | E-mail: cap_at_[hidden]
National Supercomputer Centre |
Sweden | http://www.nsc.liu.se
|
