From: "H . J . Lu" <hjl@lucon.org>
To: Uros Prestor <uros.prestor@nexsi.com>
Cc: binutils@sources.redhat.com
Subject: Re: Relocatable executables
Date: Wed, 22 Aug 2001 13:18:00 -0000 [thread overview]
Message-ID: <20010822131806.A29856@lucon.org> (raw)
In-Reply-To: <3B8412F6.FC10F886@nexsi.com>
On Wed, Aug 22, 2001 at 01:15:50PM -0700, Uros Prestor wrote:
> Hello,
>
> I am using gcc/binutils to develop software for an embedded system (MIPS
> ELF). The executable is statically linked at a fixed text address, no
> PIC. At load time I need to relocate the executable at a different
> address. Is there a way to have ld include relocation info in the
> executable?
>
`-q'
`--emit-relocs'
Leave relocation sections and contents in fully linked
exececutables. Post link analysis and optimization tools may need
this information in order to perform correct modifications of
executables. This results in larger executables.
H.J.
next prev parent reply other threads:[~2001-08-22 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 13:14 Uros Prestor
2001-08-22 13:18 ` H . J . Lu [this message]
2001-08-22 13:32 ` Uros Prestor
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=20010822131806.A29856@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=uros.prestor@nexsi.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).