public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bpshacklett at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/17251] RPATH of shared libraries doesn't follow symlinks for $ORIGIN
Date: Sun, 10 Aug 2014 17:10:00 -0000	[thread overview]
Message-ID: <bug-17251-131-x8vdUW1XDc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17251-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17251

--- Comment #1 from Brennan Shacklett <bpshacklett at gmail dot com> ---
Oops, sorry for the empty description, firefox decided to submit the form when
I hit enter.
The issue is that if a shared library has $ORIGIN in its RPATH, $ORIGIN is not
calculated as the real path of the library.

This can easily be shown with two shared libraries and a symlink:

libone.so and libtwo.so are both in a directory named ~/lib
libone.so needs libtwo.so, and has an RPATH of "$ORIGIN" so libtwo.so can be
found.
If I cd into ~/lib and run ldd on libone.so, libtwo.so is found.
If I create a symlink from ~/libone.so to ~/lib/libone.so, and run ldd on the
symlink at ~/libone.so, libtwo.so can no longer be found because $ORIGIN is not
calculated as ~ rather than ~/lib

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2014-08-10 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 17:00 [Bug dynamic-link/17251] New: " bpshacklett at gmail dot com
2014-08-10 17:10 ` bpshacklett at gmail dot com [this message]
2014-08-12  4:25 ` [Bug dynamic-link/17251] " bpshacklett at gmail dot com
2014-08-12 16:05 ` bpshacklett at gmail dot com
2014-08-14 12:47 ` fweimer at redhat dot com
2014-08-14 15:59 ` bpshacklett at gmail dot com
2014-08-18 15:28 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17251-131-x8vdUW1XDc@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).