linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Pierre Sarrazin <sarrazip@machinasapiens.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: R_PPC_REL24 relocation out of range, with trivial program
Date: Mon, 03 Apr 2000 16:46:59 -0400	[thread overview]
Message-ID: <200004032046.QAA28278@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Pierre Sarrazin <sarrazip@machinasapiens.com> of "Mon, 03 Apr 2000 16:38:49 EDT." <38E90159.DB89C967@machinasapiens.com>


	This is not fixed with the most recent toolchain RPMs (both
binutils and gcc) avaliable?

David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-04-03 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03 20:38 R_PPC_REL24 relocation out of range, with trivial program Pierre Sarrazin
2000-04-03 20:46 ` David Edelsohn [this message]
2000-04-03 21:34 ` Franz Sirl
  -- strict thread matches above, loose matches on Subject: below --
2000-03-02 23:25 Pierre Sarrazin

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=200004032046.QAA28278@mal-ach.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sarrazip@machinasapiens.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 NNTP newsgroup(s).