From: Ulrich Thiel <u-thiel@gmx.net>
To: "Aaron W. LaFramboise" <aaron98wiridge9@aaronwl.com>
Cc: binutils@sources.redhat.com
Subject: Re: PE32+ Format!
Date: Tue, 12 Apr 2005 07:33:00 -0000 [thread overview]
Message-ID: <20050412073331.GA5642@tensor.hilbert-space.com> (raw)
In-Reply-To: <425AE494.5020901@aaronwl.com>
On 15:56 Mon 11 Apr , Aaron W. LaFramboise wrote:
> The same PECOFF specification that documents the PE format presently
> supported by binutils also specifies PE32+. In each place where PE32 is
> described, changes for PE32+ are also described, making it particularly
> easy to use the specification as a guide for creating a PE32+ port based
> on the existing binutils PE support.
Exactly!
> I think it would be lots of fun to do, and fairly easy too, but I'm so
> bogged down with silly schoolwork and extracurricular projects presently
> that I can't--in good faith--volunteer to help with this.
I wouldn't call it fun :)
The problem is that I don't know anything about the binutils code. It'll
take some weeks until I understand what to do...However I'll try it.
Damn M$!
Uli
--
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x66BE0B18
fingerprint: 6530 B562 5234 9326 CDAE 5D7D 73F1 CDFD 66BE 0B18
next prev parent reply other threads:[~2005-04-12 7:33 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
2005-04-11 20:56 ` Aaron W. LaFramboise
2005-04-12 7:33 ` Ulrich Thiel [this message]
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=20050412073331.GA5642@tensor.hilbert-space.com \
--to=u-thiel@gmx.net \
--cc=aaron98wiridge9@aaronwl.com \
--cc=binutils@sources.redhat.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).