Jeff, we are averaging a half dozen support threads per week on PETSc lists/email caused by lack of RPATH in Open MPI for non-standard install locations. Can you either make the necessary environment modification more visible for novice users or implement the RPATH option?
On Wed, Sep 12, 2012 at 10:20 AM, Jeff Squyres <firstname.lastname@example.org> wrote:We have a long-standing philosophy that OMPI should add the bare minimum number of preprocessor/compiler/linker flags to its wrapper compilers, and let the user/administrator customize from there.In general, I agree with that philosophy.
That being said, a looong time ago, I started a patch to add a --with-rpath option to configure, but never finished it. :-\ I can try to get it back on my to-do list.That would be perfect.
For the moment, you might want to try the configure --enable-mpirun-prefix-by-default option, too.The downside is that we tend not to bother with the mpirun for configure and it's a little annoying to "mpirun ldd" when hunting for other problems (e.g. a missing shared lib unrelated to Open MPI).