From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: How to get COFF-format code
Date: Fri, 09 Mar 2001 07:23:26 -0500 [thread overview]
Message-ID: <4.3.2.20010309072224.00c05100@falcon.si.com> (raw)
In-Reply-To: <3AA8A8EE.1C1A8149@fiberlogic.com>
Hey, look at that. Tornado-2 (gcc-based) cross compiler supports a
flavor of coff:
C:\tmp>objdumpppc -i
BFD header file version cygnus-2.6
elf32-powerpc
(header big endian, data big endian)
powerpc:common
aixcoff-rs6000
(header big endian, data big endian)
powerpc:common
rs6000:6000
gvb
At 05:57 PM 3/9/01 +0800, Lin, Nan-Hung wrote:
>Hello,
>
>I use linux-2.4.0-test13-pre2 and
> Processor Type as 8xx
> Machine Type as TQM855L
>
>The "make" only generates ELF-format code.
>How to generate COFF-format code ?
>
>Thanks for help.
>
>
>------------------------------------------
>Carl Lin carl@fiberlogic.com
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-09 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 9:57 How to get COFF-format code Lin, Nan-Hung
2001-03-09 12:21 ` Jerry Van Baren
2001-03-09 12:23 ` Jerry Van Baren [this message]
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=4.3.2.20010309072224.00c05100@falcon.si.com \
--to=vanbaren_gerald@si.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).