From: Ralph Seguin <rseguin@rsv.ricoh.com>
To: gcc@gcc.gnu.org
Cc: gcc-help@gcc.gnu.org
Subject: Converting aout objs to elf??
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <00030911382500.31528@honey.adc.rsv.ricoh.com> (raw)
Message-ID: <20000401000000.pfkv3MfP89uHBxwJ3GtQsX-alFqAVMR6n3leR5Zzdn4@z> (raw)
Hi.
We have a library from a vendor that is compiled aout and we are using ELF
everywhere else. We do not have source to and CANNOT get them to provide an
ELF version.
I seem to remember seeing something a long time ago about converting aout
object files to ELF.
Is there an easy means of converting a library of AOUT objects into a (shared)
ELF library?
What if the library was built aout on FreeBSD 2.2.8, but we are now up to
3.3-RELEASE?
What other sorts of issues are we going to run into?
...
Thanks.
-Ralph
rseguin@rsv.ricoh.com
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 11:40 Ralph Seguin [this message]
2000-04-01 0:00 ` Ralph Seguin
2000-03-09 18:16 Mike Stump
2000-03-09 23:57 ` Philip Blundell
2000-04-01 0:00 ` Philip Blundell
2000-04-01 0:00 ` Mike Stump
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=00030911382500.31528@honey.adc.rsv.ricoh.com \
--to=rseguin@rsv.ricoh.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).