public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stuart Clarke <stuart_clarke@beeline.ag>
To: GCC <gcc@gcc.gnu.org>
Subject: Re: relocations
Date: Wed, 23 Oct 2002 06:41:00 -0000	[thread overview]
Message-ID: <200210262202.47415.stuart_clarke@beeline.ag> (raw)
In-Reply-To: <200210262157.11591.stuart_clarke@beeline.ag>

I am using the following version of GCC:

gcc version 2.95.2 20000313 (Debian GNU/Linux)

I apologise for not including this information in my first post.

Thanks again,

Stuart

On Saturday 26 October 2002 21:57, Stuart Clarke wrote:
> Hi all,
>
> I am attempting to compile a simple program on my i386 machine for an ARM
> target.  In doing this, GCC produces a relocation section in its output
> file (.rel.text).  This relocation section is of the no-addenda variety,
> however, and is incompatible with the system on which I am attempting to
> run my program.  Said system requires a .rela.text section for its
> relocations (i.e. one with addenda values).
>
> GCC doesn't seem to have a run-time option for producing a rela.text
> section rather than a rel.text one.  Is there any means by which the GCC
> source could be patched/adjusted to accomplish this?
>
> Thanks,
>
> Stuart
>
> ###########################################################################
>########## Note:
> This message is for the named person's use only.  It may contain
> confidential, proprietary or legally privileged information.  No
> confidentiality or privilege is waived or lost by any mistransmission.  If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and notify the
> sender.  You must not, directly or indirectly, use, disclose, distribute,
> print, or copy any part of this message if you are not the intended
> recipient. BEELINE Technologies and any of its subsidiaries each reserve
> the right to monitor all e-mail communications through its networks.
>
> Any views expressed in this message are those of the individual sender,
> except where the message states otherwise and the sender is authorized to
> state them to be the views of any such entity.
>
> Thank You.
> postmaster@BEELINE.ag
> ###########################################################################
>##########


#####################################################################################
Note:
This message is for the named person's use only.  It may contain confidential,
proprietary or legally privileged information.  No confidentiality or privilege
is waived or lost by any mistransmission.  If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender.  You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. BEELINE Technologies and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.

Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.

Thank You.
postmaster@BEELINE.ag
#####################################################################################

  reply	other threads:[~2002-10-23  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  6:07 relocations Stuart Clarke
2002-10-23  6:41 ` Stuart Clarke [this message]
2002-10-23 14:18 ` relocations Richard Henderson
2002-10-23 23:52 ` relocations Mike Stump

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=200210262202.47415.stuart_clarke@beeline.ag \
    --to=stuart_clarke@beeline.ag \
    --cc=gcc@gcc.gnu.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).