From: Ian Lance Taylor <ian@cygnus.com>
To: joel@OARcorp.com
Cc: gas2@cygnus.com
Subject: Re: more on powerpc-rtems ar failure
Date: Thu, 16 Apr 1998 14:43:00 -0000 [thread overview]
Message-ID: <199804162143.RAA02012@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.980416160955.26940a-100000@vespucci.advicom.net>
Date: Thu, 16 Apr 1998 16:30:24 -0500 (CDT)
From: Joel Sherrill <joel@OARcorp.com>
Will taking the default result in getting all the formats for a particular
CPU? I have tried to encourage the use of CPU-rtems for all users of CPU
and then have them use objcopy to produce the exact format required by a
board. For example, does m68k-coff (aka m68k-rtems) also include
at least m68k-aout, srecords, binary -- with m68k-elf a plus.
In general, no. You can see which formats will be supported for a
particular configuration target by looking in config.bfd. The
s-records and binary formats are always supported, as are the tekhex
and Intel hex formats. For your particular example of m68k-coff, you
will get support for m68k-coff, versados, and m68k IEEE, but not
m68k-aout or m68k-elf.
On CPUs
with both big and little endian, does it get all the "same endian"
formats?
It normally gets both big and little endian variants, if that is what
you are asking.
Ian
next prev parent reply other threads:[~1998-04-16 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-16 13:26 Joel Sherrill
1998-04-16 14:03 ` Ian Lance Taylor
1998-04-16 15:36 ` Joel Sherrill
1998-04-16 14:43 ` Ian Lance Taylor [this message]
1998-04-16 14:55 ` Joel Sherrill
1998-04-16 14:55 ` Ian Lance Taylor
1998-04-16 15:02 ` Joel Sherrill
1998-04-16 15:36 ` Ian Lance Taylor
1998-04-17 5:55 ` Joel Sherrill
1998-04-17 8:44 ` Ian Lance Taylor
1998-04-17 9:01 ` Joel Sherrill
1998-04-17 9:01 ` Ian Lance Taylor
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=199804162143.RAA02012@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=joel@OARcorp.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).