public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: geoffk@cygnus.com, libc-hacker@sourceware.cygnus.com,
	binutils@sourceware.cygnus.com, ian@zembu.com
Subject: Re: glibc 2.1 and gabi
Date: Fri, 21 Jul 2000 09:07:00 -0000	[thread overview]
Message-ID: <20000721090659.A10200@lucon.org> (raw)
In-Reply-To: <20000721090125.A10155@lucon.org>

On Fri, Jul 21, 2000 at 09:01:25AM -0700, H . J . Lu wrote:
> > previously -rpath did only set DT_RPATH, it now also sets DT_RUNPATH.
> > As I understand it DT_RUNPATH is supposed to replace DT_RPATH in the
> > new ELF specs, but with slightly different semantics (at least on some
> > platfroms).  This makes me wonder whether setting both is really such
> 
> I don't think it should do any harm. You only enable it with
> --enanle-new-dtags. The ld.so should check DT_RUNPATH first and
> then DT_RPATH. It will skip DT_RPATH if DT_RUNPATH is found. If it
> doesn't know DT_RUNPATH at all, it should just ignore it.
> 

FYI, from the new gABI:

-----
A fourth search facility, the dynamic array tag DT_RPATH, has been
moved to level 2 in the ABI. It provides a colon-separated list of
directories to search. Directories specified by DT_RPATH are searched
before directories specified by LD_LIBRARY_PATH. 

If both DT_RPATH and DT_RUNPATH entries appear in a single object's
dynamic array, the dynamic linker processes only the DT_RUNPATH entry. 
----


H.J.

  reply	other threads:[~2000-07-21  9:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-20 11:42 H . J . Lu
2000-07-20 13:23 ` Geoff Keating
2000-07-20 13:57   ` H . J . Lu
2000-07-20 15:47     ` Geoff Keating
2000-07-20 15:52       ` H . J . Lu
2000-07-20 16:12         ` Geoff Keating
2000-07-20 17:10           ` H . J . Lu
2000-07-20 20:28             ` Geoff Keating
2000-07-20 21:15               ` H . J . Lu
2000-07-20 23:13                 ` Geoff Keating
2000-07-20 23:22                   ` H . J . Lu
2000-07-21  0:19                     ` Mark Kettenis
2000-07-21  9:01                       ` H . J . Lu
2000-07-21  9:07                         ` H . J . Lu [this message]
2000-07-20 12:06 Nick Clifton
2000-07-20 12:12 ` H . J . Lu
2000-07-20 12:26 Nick Clifton
2000-07-20 12:41 ` H . J . Lu
2000-07-23 20:18   ` Andrew Cagney
2000-07-23 21:01     ` H . J . Lu
2000-07-20 13:17 Nick Clifton
2000-07-20 13:55 ` H . J . Lu
2000-07-20 14:12 Nick Clifton
2000-07-20 15:00 ` H . J . Lu
2000-07-24 10:52 Nick Clifton

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=20000721090659.A10200@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sourceware.cygnus.com \
    --cc=geoffk@cygnus.com \
    --cc=ian@zembu.com \
    --cc=kettenis@wins.uva.nl \
    --cc=libc-hacker@sourceware.cygnus.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).