The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Origins of the SGS (System Generation Software) and COFF (Common Object File Format)
Date: Sat, 25 Feb 2023 20:34:09 +0100	[thread overview]
Message-ID: <20230225193409.wspfB%steffen@sdaoden.eu> (raw)
In-Reply-To: <202302251928.31PJSXc1004140@freefriends.org>

arnold@skeeve.com wrote in
 <202302251928.31PJSXc1004140@freefriends.org>:
 |Arno Griffioen via TUHS <tuhs@tuhs.org> wrote:
 |> On Fri, Feb 24, 2023 at 05:45:16AM -0700, arnold@skeeve.com wrote:
 |>> With tar and cpio, ar apparently fell out of use as a general
 |>> archiver, and today it's only used for libraries of relocatable
 |>> object files.
 |>
 |> 'ar' is alive and well as the archive format for .deb files though, \
 |> so it 
 |> could be argued that it's actually hugely in use as an archiver all \
 |> across 
 |> the world :)
 |>
 |>        Bye, Arno.
 |
 |I wasn't aware of that. Thanks.

It is also used during the build phase of some programs (groff
last i looked).  Ie they build their support objects, and instead
of having make rules with $(OBJ) they simply link against the
library.  (I have not looked whether they build with -fPIC
/ -fPIE, to outrule your "relocatable", that is.)

 --End of <202302251928.31PJSXc1004140@freefriends.org>

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  reply	other threads:[~2023-02-25 19:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 20:16 [TUHS] " segaloco via TUHS
2023-02-22 22:20 ` [TUHS] " Clem Cole
2023-02-23  0:17   ` segaloco via TUHS
2023-02-23  6:30   ` Lars Brinkhoff
2023-02-23 14:25     ` KenUnix
2023-02-23 19:37     ` Warner Losh
2023-02-24 17:01       ` Rich Salz
2023-02-23 16:49   ` Paul Winalski
2023-02-23 18:38     ` segaloco via TUHS
2023-02-23 20:40       ` Paul Winalski
2023-02-24 12:45     ` arnold
2023-02-24 13:13       ` Arno Griffioen via TUHS
2023-02-25 19:28         ` arnold
2023-02-25 19:34           ` Steffen Nurpmeso [this message]
2023-02-24 14:01       ` Harald Arnesen
2023-02-25  2:07     ` Dave Horsfall
2023-02-25 15:30       ` Clem Cole
2023-02-25 17:29         ` Paul Winalski
2023-02-23 15:13 Noel Chiappa
2023-02-23 21:37 Paul Ruizendaal
2023-02-23 22:11 ` segaloco via TUHS
2023-02-24  0:07   ` segaloco via TUHS
2023-02-25 20:14 Brian Walden
2023-02-26 15:51 Paul Winalski

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=20230225193409.wspfB%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=arnold@skeeve.com \
    --cc=tuhs@tuhs.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 NNTP newsgroup(s).