From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: i-love-spam <i-love-spam@yandex.ru>, binutils@sourceware.org
Subject: Re: ARM-ELF -> PE-COFF with objcopy
Date: Tue, 28 Apr 2009 14:25:00 -0000 [thread overview]
Message-ID: <49F7146C.6000600@gmail.com> (raw)
In-Reply-To: <m3mya0kgpb.fsf@google.com>
Ian Lance Taylor wrote:
> I don't really understand what you are trying to do or why you are using
> ELF at all. Why not just compile your code into PE format in the first
> place?
>
> The only realistic way that you can create a PE DLL is to compile code
> with a PE compiler. Otherwise you aren't going to get the right code
> sequences and relocations. It is theoretically possible to pursue other
> paths but they are all going to be complex and difficult.
What about this whole ELF->PE post-linking stuff that symbian arm-eabi
targets apparently do? Could that be adapted for wince?
cheers,
DaveK
next prev parent reply other threads:[~2009-04-28 14:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 9:45 pps
2009-04-27 14:33 ` Nick Clifton
2009-04-27 16:26 ` pps
2009-04-27 21:21 ` i-love-spam
2009-04-27 22:49 ` Ian Lance Taylor
2009-04-28 7:24 ` i-love-spam
2009-04-28 7:45 ` Nick Clifton
2009-04-28 8:31 ` i-love-spam
2009-04-28 10:44 ` Nick Clifton
2009-05-08 20:55 ` i-love-spam
2009-05-09 17:20 ` Dave Korn
2009-04-28 14:15 ` Ian Lance Taylor
2009-04-28 14:25 ` Dave Korn [this message]
2009-04-28 15:46 ` pps
2009-04-28 16:07 ` Dave Korn
2009-04-28 16:56 ` Daniel Jacobowitz
2009-04-28 17:29 ` Pedro Alves
2009-04-28 17:33 ` Daniel Jacobowitz
2009-04-28 21:09 ` Dave Korn
2009-05-07 6:58 ` pps
2009-05-07 9:38 ` Vincent R.
2009-05-07 12:27 ` Dave Korn
2009-05-07 12:34 ` Vincent R.
2009-05-08 8:31 ` pps
2009-05-08 8:32 ` pps
2009-04-28 16:44 ` Ian Lance Taylor
2009-04-28 16:52 ` pps
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=49F7146C.6000600@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=binutils@sourceware.org \
--cc=i-love-spam@yandex.ru \
--cc=iant@google.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).