Jeff Squyres wrote:
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?
Ensure that the underlying compiler see this in the environment when it
is run.
Thx.John
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
enc
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/ued
