Am 12.11.2012 um 10:53 schrieb Iliev, Hristo:
> Hi, Reuti,
>
> Here is an informative article on dynamic libraries path in OS X:
>
> https://blogs.oracle.com/dipol/entry/dynamic_libraries_rpath_and_mac
Thx. - Reuti
> The first comment is very informative too.
>
> Kind regards,
> Hristo
> --
> Hristo Iliev, Ph.D. -- High Performance Computing
> RWTH Aachen University, Center for Computing and Communication
> Rechen- und Kommunikationszentrum der RWTH Aachen
> Seffenter Weg 23, D 52074 Aachen (Germany)
>
>> -Original Message-
>> From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org]
>> On Behalf Of Reuti
>> Sent: Sunday, November 11, 2012 10:18 PM
>> To: Open MPI Users
>> Subject: Re: [OMPI users] Setting RPATH for Open MPI libraries
>>
>> Hi,
>>
>> Am 05.11.2012 um 04:41 schrieb Jed Brown:
>>
>>> 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?
>>
>> For curiosity: on Mac OS X it finds the necessary library automatically,
> by
>> which setting is this achieved? `otool -L ` lists the correct one,
> which
>> was used during compilation.
>>
>> -- Reuti
>>
>>
>>>
>>> On Wed, Sep 12, 2012 at 1:52 PM, Jed Brown wrote:
>>> On Wed, Sep 12, 2012 at 10:20 AM, Jeff Squyres
>> 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).
>>>
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
