From: Nick Clifton <nickc@redhat.com>
To: Ulrich Thiel <u-thiel@gmx.net>
Cc: binutils@sources.redhat.com
Subject: Re: PE32+ Format!
Date: Mon, 11 Apr 2005 15:55:00 -0000 [thread overview]
Message-ID: <425A9D7E.4030509@redhat.com> (raw)
In-Reply-To: <20050408164035.GB5975@tensor.hilbert-space.com>
Hi Ulrich,
> Is there any possibility to convert PE32+ (remark the +) object files to
> x86_64 ELF64 object files?
At the moment no. Nobody has contributed code to support the PE32+
format, so binutils cannot read it, let alone convert it.
> I've heard that there are only a few changes in this new PE32+ file format.
Would you be interested in writing a patch to add this support then ?
By the way - is there any public documentation on the PE32+ format
available ?
Cheers
Nick
next prev parent reply other threads:[~2005-04-11 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 16:40 Ulrich Thiel
2005-04-11 15:55 ` Nick Clifton [this message]
2005-04-11 20:56 ` Aaron W. LaFramboise
2005-04-12 7:33 ` Ulrich Thiel
2005-04-11 16:04 Jan Beulich
2005-04-11 17:37 ` Christopher Faylor
2005-04-11 17:50 Ulrich Thiel
2005-04-12 6:42 Jan Beulich
2005-04-12 13:46 ` Christopher Faylor
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=425A9D7E.4030509@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=u-thiel@gmx.net \
/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).