The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: henry.r.bent@gmail.com (Henry Bent)
Subject: [TUHS] shared objects in Unix
Date: Thu, 29 Mar 2018 18:01:42 -0400	[thread overview]
Message-ID: <CAEdTPBdWS6W0om+4HeSHmNSZb-NQEhZyzmFWyS3EmN=EhmXzOw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VQvhHKemfOOvVFSu9K+Go1LB5e2Ck214KdLJvtE--z8Hg@mail.gmail.com>

On 29 March 2018 at 17:37, Paul Winalski <paul.winalski at gmail.com> wrote:

>
> What is the history of shared objects on Unix?  When did they first
> appear, and with what object/executable file format?  The a.out ZMAGIC
> format doesn't seem to support them.  I don't recall if COFF does.
>

IRIX 4 had COFF shared libraries, barely.  The OS included libc_s, libgl_s,
and maybe one or two other things.  They were very difficult and
time-consuming to create, and if you had external dependencies then things
were even worse.

-Henry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180329/4eeeddb3/attachment.html>


  reply	other threads:[~2018-03-29 22:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 21:37 Paul Winalski
2018-03-29 22:01 ` Henry Bent [this message]
2018-03-29 22:26 ` Warner Losh
2018-03-29 23:11 ` Dave Horsfall
2018-03-29 23:22   ` Warner Losh
2018-03-29 23:24   ` Larry McVoy
2018-03-30  0:22     ` Clem Cole
2018-03-30  1:46       ` Larry McVoy
2018-03-30  4:28         ` Clem cole
2018-03-30 20:52           ` Jon Forrest
2018-03-30 22:42             ` Clem Cole
2018-03-30 23:29               ` Paul Winalski
2018-04-03 15:49               ` Derek Fawcus
2018-03-30  1:20   ` Lyndon Nerenberg
2018-03-30  0:40 ` Clem Cole
2018-03-30  1:35   ` Charles H. Sauer
2018-03-30  2:10     ` Larry McVoy
2018-03-30  2:34       ` Charles H. Sauer
2018-03-30  3:04         ` Warner Losh
2018-03-30 20:33         ` Charles H Sauer
2018-03-30  3:00   ` Ron Natalie
2018-03-30 21:53   ` Steve Johnson

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='CAEdTPBdWS6W0om+4HeSHmNSZb-NQEhZyzmFWyS3EmN=EhmXzOw@mail.gmail.com' \
    --to=henry.r.bent@gmail.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 NNTP newsgroup(s).