public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: K.Peeters@damtp.cam.ac.uk
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: <19990621023358.8435.qmail@daffy.airs.com> (raw)
In-Reply-To: <14189.24404.190234.153358@hopf.amtp.cam.ac.uk>

   From: Kasper Peeters <K.Peeters@damtp.cam.ac.uk>
   Date: Sun, 20 Jun 1999 22:38:28 +0100 (BST)

   >    Is there a simple way to add an RPATH to an already existing
   >    executable using binutils?  (this is on i386 elf)
   > 
   > No.

   Ok, let me ask this in a different way ;-)

   Is there a _complicated_ way to add an RPATH to an already existing
   executable using binutils? 

   I looked at libbfd for half an hour, and it seems like I could just
   read the executable file using bfd_openr and friends, add the rpath to
   the private data and write it back. But I find it hard to believe that
   nobody else has had a need for such a program before. 

You could do that, but it wouldn't work.  That is because RPATH goes
into a loadable segment.  When you changed the size of the RPATH, you
would be adjusting the position of everything else in that segment.
The program was linked to expect things to be at a certain position.
When you change that position, the program will no longer work.

   Is libbfd capable of doing this or is more trickery involved that I am
   not aware of?

libbfd is capable of changing the RPATH in certain circumstances which
Richard mentioned: when you can find some place to squeeze it in.  But
you have to do all the work yourself.

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.  Otherwise, they rebuild the program, or in extreme
cases they hack the dynamic linker.

Ian

  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 [this message]
1999-07-01  0:00       ` Kasper Peeters

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=19990621023358.8435.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=K.Peeters@damtp.cam.ac.uk \
    --cc=binutils@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).