From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Honor executables DT_RUNPATH for dlopen
Date: Tue, 05 Nov 2002 20:04:00 -0000 [thread overview]
Message-ID: <200211060404.gA644dK18292@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Thursday, 10 October 2002 16:21:55 +0200 <20021010162155.Y3451@sunsite.ms.mff.cuni.cz>
That change is not correct. The ELF spec says that DT_RUNPATH applies to
"only the immediate dependencies of the executable or shared object
containing the DT_RUNPATH entry." I'm not aware of anything that specifies
dlopen in enough detail that it couldn't do whatever it likes. But it
seems consistent with the spec for dlopen not to be affected by any
DT_RUNPATH (except for dependencies being affected by a DT_RUNPATH within a
dlopen'd dependent object). The application or library can use whatever
prefix it put in its DT_RUNPATH on the strings it passes to dlopen directly.
prev parent reply other threads:[~2002-11-06 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 23:42 Jakub Jelinek
2002-11-05 20:04 ` Roland McGrath [this message]
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=200211060404.gA644dK18292@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).