On Mon, 16 Jun 2003, Laurence Viry wrote:
> % mpicc -showme -c MPI_C_SAMPLE.c
> >cc -I/usr/local/mpi/lam-6.5.9/include -c MPI_C_SAMPLE.c
>
> then for the link:
>
> % mpicc -o hello MPI_C_SAMPLE.o -showme
> > cc -I/usr/local/mpi/lam-6.5.9/include -L/usr/local/mpi/lam-6.5.9/lib -o hello MPI_C_SAMPLE.o -llammpio -lpmpi -llamf77mpi -lmpi -llam -laio -lutil
>
> without -showme I had :
>
> ld:
> Unresolved:
> lam_mpi_comm_world
> lam_mpi_int
Keep in mind that -I and -L only *add* paths to the compiler/linker's
default search paths. The other paths (e.g., /usr/include, /usr/lib) will
still be used, and depending on how your compiler/linker works, it may
still find an <mpi.h> or libmpi.a in a directory other than where your LAM
libraries are installed.
It sounds like this may be what is happening -- particularly if the LAM
symbols are not found by the linker. Can you double check that no files
of conflicting names can be found in the default compiler/linker paths?
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
