From: Kasper Peeters <K.Peeters@damtp.cam.ac.uk>
To: Ian Lance Taylor <ian@zembu.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: adding rpath to existing executable
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <14189.60129.337013.447650@hopf.amtp.cam.ac.uk> (raw)
In-Reply-To: <19990621023358.8435.qmail@daffy.airs.com>
> I've never known anybody to want to change the RPATH of a linked
> executable. Mostly, people just run a shell script which sets
> LD_LIBRARY_PATH.
I am on a system which has glibc-2.0, but I _need_ glibc-2.1 for my
own programs (because glibc-2.0 contains a fatal bug that my program
is triggering). If I set LD_LIBRARY_PATH to point to my glibc-2.1
directory, the glibc-2.0 dynamic linker prefers the glibc-2.1
libraries over the glibc-2.0 ones and (of course) fails.
I don't want to wrap all of my stuff in scripts, and I can't really
either, since some of them are dynamically loaded modules themselves
while others call old glibc-2.0 ones. It's going to be a mess that
way.
> Otherwise, they rebuild the program, or in extreme
> cases they hack the dynamic linker.
I could modify the dynamic linker for glibc-2.1 to look at
LD_LIBRARY_PAT2 instead of LD_LIBRARY_PATH. Guess that's the easiest
way out.
Kasper
prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Kasper Peeters
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Kasper Peeters
1999-07-01 0:00 ` Marty Leisner
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Kasper Peeters [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=14189.60129.337013.447650@hopf.amtp.cam.ac.uk \
--to=k.peeters@damtp.cam.ac.uk \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).