From: "John Kastner, Ph.D." <kastner@home.com>
To: <cygwin@sourceware.cygnus.com>
Subject: objcopy converting a.out to ELF with DWARF2 for i386
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <004301be69a3$043ffa40$3ca6b6cc@kastner.arium.com> (raw)
Message-ID: <19990331194500.2JD6qtBp71wQhiArq8FhP1ERVPWQxu3c1lGV4lXVDtU@z> (raw)
The company I work for would like to work with ELF/DWARF2 files.
However our user base still uses older a.out. We are looking into using
objcopy on a.out to produce ELF/DWARF2. We don't require perfect
fidelity but we are looking for a strong interim solution. We only need
an i386 solution (a.out-i386 to elf32-i386).
Is anyone out there currently doing a similar extension to the tools?
Is anyone out there interested in receiving our extensions if and when
we produce them?
I welcome helpful comments and suggestions.
John Kastner, Ph.D.
kastner@home.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-03-31 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-08 12:35 John Kastner, Ph.D. [this message]
[not found] ` < 004301be69a3$043ffa40$3ca6b6cc@kastner.arium.com >
1999-03-08 13:13 ` Chris Faylor
1999-03-31 19:45 ` Chris Faylor
1999-03-31 19:45 ` John Kastner, Ph.D.
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='004301be69a3$043ffa40$3ca6b6cc@kastner.arium.com' \
--to=kastner@home.com \
--cc=cygwin@sourceware.cygnus.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).