public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, rseguin@rsv.ricoh.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: Converting aout objs to elf??
Date: Thu, 09 Mar 2000 18:16:00 -0000	[thread overview]
Message-ID: <200003100216.SAA03962@kankakee.wrs.com> (raw)

> From: Ralph Seguin <rseguin@rsv.ricoh.com>
> To: gcc@gcc.gnu.org
> Date: Thu, 9 Mar 2000 11:35:04 -0800
> Cc: gcc-help@gcc.gnu.org

> 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.

Dump em, it'll save you some time and pain.

> 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?

Sure, just pull out objcopy, and extend it to handle the relocs on
your platform well, and presto, no problem.  Well, you might need to
have ld remap the syms for you, byt other than that, it should just
work.

WARNING: multiple messages have this Message-ID
From: Mike Stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, rseguin@rsv.ricoh.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: Converting aout objs to elf??
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200003100216.SAA03962@kankakee.wrs.com> (raw)
Message-ID: <20000401000000.IpTRJvsuO6xyo0PvSaLjfvzzdJC7NooaDfPlJFH-8Y4@z> (raw)

> From: Ralph Seguin <rseguin@rsv.ricoh.com>
> To: gcc@gcc.gnu.org
> Date: Thu, 9 Mar 2000 11:35:04 -0800
> Cc: gcc-help@gcc.gnu.org

> 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.

Dump em, it'll save you some time and pain.

> 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?

Sure, just pull out objcopy, and extend it to handle the relocs on
your platform well, and presto, no problem.  Well, you might need to
have ld remap the syms for you, byt other than that, it should just
work.

             reply	other threads:[~2000-03-09 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-09 18:16 Mike Stump [this message]
2000-03-09 23:57 ` Philip Blundell
2000-04-01  0:00   ` Philip Blundell
2000-04-01  0:00 ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
2000-03-09 11:40 Ralph Seguin
2000-04-01  0:00 ` Ralph Seguin

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=200003100216.SAA03962@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=rseguin@rsv.ricoh.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).