See this thread on the pkg-openmpi-maintainers list:
http://lists.alioth.debian.org/pipermail/pkg-openmpi-maintainers/2009-January/001278.html
On Jan 13, 2009, at 12:52 PM, Ralf Wildenhues wrote:
Hello Jeff,
* Jeff Squyres wrote on Tue, Jan 13, 2009 at 03:39:28PM CET:
On Jan 13, 2009,
Hello Jeff,
* Jeff Squyres wrote on Tue, Jan 13, 2009 at 03:39:28PM CET:
> On Jan 13, 2009, at 4:54 AM, Manuel Prinz wrote:
>>
>> You have to pass --disable-rpath explicitely. Building with rpath is
>> still the default. I verified by building without passing any option
>> to configure and the r
Just for the web archives: per some off-list discussion, we decided
not to take the patch because the Debian guys have a simpler
workaround for what they want.
On Jan 13, 2009, at 4:54 AM, Manuel Prinz wrote:
Am Montag, den 12.01.2009, 18:04 -0500 schrieb Jeff Squyres:
I don't see much ha
Am Montag, den 12.01.2009, 18:04 -0500 schrieb Jeff Squyres:
> I don't see much harm in including this as long as rpath builds are
> still the default. If there's a non-default option to disable rpath
> builds, that would be fine with me.
>
> Does this patch disable rpath by default, or do yo
I don't see much harm in including this as long as rpath builds are
still the default. If there's a non-default option to disable rpath
builds, that would be fine with me.
Does this patch disable rpath by default, or do you have to explicitly
use the --disable-rpath flag to configure?
O
On 8 January 2009 at 16:45, Manuel Prinz wrote:
| Hi,
|
| attached you'll find a (trivial) patch against the latest svn trunk
| (r20227) that adds a --disable-rpath to configure, so libraries can be
| build with rpath disabled. The reason for adding this feature that was
| that rpath is often pro
