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: Thu, 14 Aug 2014 15:59:00 -0000	[thread overview]
Message-ID: <bug-17251-131-8qdqMwztK4@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 #5 from Brennan Shacklett <bpshacklett at gmail dot com> ---
Well I defined __realpath in dl-realpath.c and included that into
rtld-routines, doesn't that allow the linker to use it?
I'm not sure what you mean about __realpath being broken with a non null 2nd
argument, the version which I defined in dl-realpath doesn't even handle a NULL
second argument (I didn't think it was necessary). Are you saying I should
rewrite the dl-realpath version to handle that NULL and dynamically allocate
its own memory?

There is a more detailed explanation in my mailing list post here:
https://sourceware.org/ml/libc-alpha/2014-08/msg00160.html if you want more
details.

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


  parent reply	other threads:[~2014-08-14 15:59 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 ` [Bug dynamic-link/17251] " bpshacklett at gmail dot com
2014-08-12  4:25 ` 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 [this message]
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-8qdqMwztK4@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).