I'm not sure what you're asking -- mpicxx just fork/exec's the
underlying compiler (you can "mpicxx --showme" to see what it does).
What do you need it to do with LD_RUN_PATH?
On Aug 3, 2009, at 4:21 PM, John R. Cary wrote:
In the latest versions of libtool, the runtime library path is
encoded with
a statement like:
LD_RUN_PATH="/scr_multipole/cary/facetsall/physics/uedge/par/
uecxxpy/.libs:/contrib/babel-1.4.0-r6662p1-shared/lib:/scr_multipole/
cary/facetsall/physics/uedge/par/uecxxpy:/scr_multipole/cary/
volatile/uedge-r1161-par/lib:"
mpicxx -g -O2 -fno-strict-aliasing -Wall -pthread -g -O2 -pipe
-march=athlon -Wall -Wno-unused -o .libs/uecxxpy ../uebase/uedge.o
libuecxxpy.a ./.libs/libuecxxpycli.so
-L/contrib/babel-1.4.0-r6662p1-shared/lib
/contrib/babel-1.4.0-r6662p1-shared/lib/libsidlstub_cxx.so
/contrib/babel-1.4.0-r6662p1-shared/lib/libsidl.so -lm
/contrib/babel-1.4.0-r6662p1-shared/lib/libparsifal.so
/contrib/babel-1.4.0-r6662p1-shared/lib/libchasmlite.so -ldl
../uebase/libuebase.a
/scr_multipole/cary/volatile/txbase-r246-ser/lib/gcc4/libtxbase.a -
pthread
using the LD_RUN_PATH variable.
It seems as if mpicxx ignores this. Is there a way to get
back to where LD_RUN_PATH works?
Thx....John Cary
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
jsquy...@cisco.com
