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] Support LD_USE_LOAD_BIAS
Date: Sat, 22 Nov 2003 02:18:00 -0000 [thread overview]
Message-ID: <200311220044.hAM0iKg3019091@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Friday, 21 November 2003 23:32:25 +0100 <20031121223225.GW12344@sunsite.ms.mff.cuni.cz>
> LD_USE_LOAD_BIAS is what Ulrich suggested. LD_INHIBIT_PRELINK can be
> misleading IMHO. One thing is if prelink info is or is not used
> and a different is whether library load biases are honored or not.
I see. Perhaps LD_ALWAYS_RELOCATE? The reason I dislike "USE_LOAD_BIAS"
is that it describes the implementation issue more than it describes what
is going on from the user's perspective.
Thanks,
Roland
next prev parent reply other threads:[~2003-11-22 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 0:16 Jakub Jelinek
2003-11-22 0:28 ` Jakub Jelinek
2003-11-22 0:37 ` Roland McGrath
2003-11-22 0:44 ` Jakub Jelinek
2003-11-22 2:18 ` Roland McGrath [this message]
2003-11-22 3:01 ` Ulrich Drepper
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=200311220044.hAM0iKg3019091@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).