Btw, as we tell everyone on this list, if you're just starting with mpi, we strongly advise you to use open mpi, not lam mpi. Lam has no active developers anymore (it hasn't for years). We all move to open mpi years ago.
-jms
Sent from my PDA. No type good.
________________________________
From: lam-bounces_at_[hidden] <lam-bounces_at_[hidden]>
To: General LAM/MPI mailing list <lam_at_[hidden]>
Sent: Mon Apr 12 00:37:35 2010
Subject: Re: LAM: cannot find -lopen-rte
Yes, you are right
There is a difference between fedora 8 and opensuse lib paths.
In opensuse the lam is created in /usr/local/lib and the search to find the folder under /usr/lib/lam is unsuccessful. so I want to know how I can reconfigure suse in order to force it to make lam in the expected path or change lam to look in /usr/local/lib instead of /usr/lib/lam.
P.S there exists a directory /usr/lib/mpi/gcc/openmpi that i have not created. may it be possible that lam looks in the specified path?
P.S in my fedora 8 machine mpicc generate the following code:
gcc -I/usr/local/include -pthread -o cpi.exe cpi.c -L/usr/local/lib -llammpio -llamf77mpi -lmpi -llam -lutil -ldl
but
in opensuse:
gcc -I/usr/lib/mpi/gcc/openmpi/include/openmpi -I/usr/lib/mpi/gcc/openmpi/include -pthread -o cpi.exe cpi.c -L/usr/lib/mpi/gcc/openmpi/lib -lmpi -lopen-rte -lopen-pal -ldl -Wl,--export-dynamic -lnsl -lutil -lm -ldl
|
