I have just uploaded a patch to a long-existing ticket:
https://svn.open-mpi.org/trac/ompi/ticket/376
The bitbucket with this work is here:
https://bitbucket.org/jsquyres/ompi-rpath/changesets
I've put the wrapper rpath flags issue on the agenda for the December dev
meeting.
On Nov 4
On Nov 11, 2012, at 5:11 PM, Reuti wrote:
> Then it works again and the RPATH is included. Why is the necessary -L
> argument removed by the wrapper during compilation if OMPI_LDFLAGS for
> additonal flags is used?
When you specify OMPI_LDFLAGS, it *replaces* the LDFLAGS in the wrapper
compile
-
>> 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,
>>
>>
0: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 Ope
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 use
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 use
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
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 philoso
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.
That being said, a looong time ago, I started a patch to add a --with-rpath
option to configure, b
On Tue, Sep 11, 2012 at 2:29 PM, Reuti wrote:
> With "user" you mean someone compiling Open MPI?
Yes
Am 11.09.2012 um 20:22 schrieb Jed Brown:
> I want to avoid the user
With "user" you mean someone compiling Open MPI?
-- Reuti
> having to figure that out. MPICH2 sets RPATH by default when installed to
> nonstandard locations and I think that is not a bad choice. Usually
> applications are
I want to avoid the user having to figure that out. MPICH2 sets RPATH by
default when installed to nonstandard locations and I think that is not a
bad choice. Usually applications are compiled differetly when the want to
switch between debug and optimized (or other reasons for selecting a
different
Hi,
Am 08.09.2012 um 14:46 schrieb Jed Brown:
> Is there a way to configure Open MPI to use RPATH without needing to manually
> specify --with-wrapper-ldflags=-Wl,-rpath,${prefix}/lib (and similar for
> non-GNU-compatible compilers)? ___
What do you
13 matches
Mail list logo
