public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: joel@OARcorp.com
To: gas2@cygnus.com
Subject: powerpc problems??
Date: Fri, 02 Apr 1999 06:17:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.990402082133.11598E-100000@oar3remote> (raw)

Hi,

I have reports from one of the RTEMS testers that he is having trouble
linking applications with binutils-2.9.1.0.22b for powerpc-rtems
(powerpc-eabi) and m68k-rtems (m68k-coff).  I am using binutils 2.9.1
and not seeing his problems.  Other rtems targets do not show any
problems.

Other than that, I am using egcs 1.1.2 and he is using the current CVS
source off that branch, so I think we are in close sync on that.

Are there any known problems that we might have run into here?

--joel
Joel Sherrill                    Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985



             reply	other threads:[~1999-04-02  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-02  6:17 joel [this message]
1999-04-02  7:09 ` H.J. Lu

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=Pine.LNX.3.96.990402082133.11598E-100000@oar3remote \
    --to=joel@oarcorp.com \
    --cc=gas2@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).