public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: John Reiser <jreiser@bitwagon.com>
To: binutils@sourceware.org
Subject: Re: partial linking that resolves relocations
Date: Thu, 19 May 2011 17:33:00 -0000	[thread overview]
Message-ID: <4DD5548A.7010906@bitwagon.com> (raw)
In-Reply-To: <BANLkTi=UftdOY81qjBiiK01NLUY-BymYyQ@mail.gmail.com>

On 05/18/2011 12:50 AM, Yni Mous wrote:

> Is there a way to combine object files (1.o and 2.o) to produce another
> object file (similar to ld -i) with the relocations "resolved"?

There is no direct way, although there should be: for instance,
some additional flag such that "ld -r" would resolve what it could,
instead of just accumulating the relocations for later resolution.

There might be a work-around, however.  Run "ld -r", then run
"objcopy --strip-symbol=foo".  If objcopy interprets this favorably,
then objcopy must resolve the relocations that depend on 'foo'.

-- 

  parent reply	other threads:[~2011-05-19 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  7:50 Yni Mous
2011-05-18 23:57 ` Ian Lance Taylor
2011-05-19 17:33 ` John Reiser [this message]
2011-05-19 17:50   ` John Reiser

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=4DD5548A.7010906@bitwagon.com \
    --to=jreiser@bitwagon.com \
    --cc=binutils@sourceware.org \
    /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).