[rust-dev] Impending change in RPATH behavior when linking to Rust dynamic libraries

Stepan Koltsov stepan.koltsov at gmail.com
Sat Jul 12 16:43:10 PDT 2014


On Wed, Jul 9, 2014 at 8:48 PM, Patrick Walton <pcwalton at mozilla.com> wrote:

> On 7/9/14 7:42 AM, Bob Ippolito wrote:
>
>> This seems like madness. No other programming language out there that
>> I've seen requires developers to mangle these environment variables.
>>
>
> Also, when installing Rust you don't have to mangle these environment
> variables, since the libraries will be placed into the right place. This
> should only impact anyone who builds from source without installing.
>


It also impacts people who:
— want to have several versions of rust side by side to investigate problems
— need different fixed per-project environments
— don't have permission to write into /usr/local (typically on shared
servers)
— don't want to have a mess in /usr/local


As detailed in the meeting where this decision was made, Linux distros
> really dislike it when you mess with rpath; it's a deal-breaker in many
> cases.
>

I don't know about all Linux distros, but apparently Ubuntu is OK about
rpath:

$ objdump -x /usr/lib/jvm/java-7-openjdk-amd64/bin/java | grep RPATH
  RPATH
$ORIGIN/../lib/amd64/jli:$ORIGIN/../lib/amd64:$ORIGIN/../jre/lib/amd64

Anyway, rust can be built without rpath for linux distros, and with rpath
for downloading from site.

-- 
Stepan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rust-dev/attachments/20140713/9b9d81ca/attachment.html>


More information about the Rust-dev mailing list