From: Greg 'groggy' Lehey <grog@lemis.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] ar libraries [was: Speaking commands [Was: Bell System Technical Journal archive]]
Date: Thu, 19 Jul 2018 14:59:09 +1000 [thread overview]
Message-ID: <20180719045909.GD54853@eureka.lemis.com> (raw)
In-Reply-To: <201807181739.w6IHdUZW004045@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Wednesday, 18 July 2018 at 11:39:30 -0600, arnold@skeeve.com wrote:
> "John P. Linderman" <jpl.jpl@gmail.com> wrote:
>
>> I guess it [ar] lives on in the creation of "libraries" that could be
>> loaded by compilers, although I think shared objects have largely replaced
>> archive files, and I'm not sure if archive files are even accepted any more.
>
> Archive files (static libraries) are alive and well and work just fine,
> on Linux and every other *nix that I know about. The format is even
> used on Windows for static libraries and for whatever you call them when
> linking dynamic libraries (they provide the symbols, but not the dll).
This has been the case for FreeBSD too for as long as I can recall. I
thought it was the case for all .a libraries.
$ uname -a
FreeBSD eureka.lemis.com 10.2-STABLE FreeBSD 10.2-STABLE #2 r290972: Wed Nov 25 11:38:38 AEDT 2015 grog@stable.lemis.com:/usr/obj/eureka/home/src/FreeBSD/svn/10/sys/GENERIC amd64
$ file /usr/lib/libc.a
/usr/lib/libc.a: current ar archive
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2018-07-19 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:33 [TUHS] Speaking commands [Was: Bell System Technical Journal archive] Nemo
2018-07-17 13:20 ` arnold
2018-07-17 14:39 ` John P. Linderman
2018-07-18 17:39 ` arnold
2018-07-19 4:59 ` Greg 'groggy' Lehey [this message]
2018-07-19 15:29 ` [TUHS] ar libraries [was: Speaking commands [Was: Bell System Technical Journal archive]] Paul Winalski
2018-07-19 16:12 ` John P. Linderman
2018-07-20 23:01 ` [TUHS] Speaking commands [Was: Bell System Technical Journal archive] Kurt H Maier
2018-07-18 0:56 ` Ron Natalie
2018-07-18 3:54 ` arnold
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=20180719045909.GD54853@eureka.lemis.com \
--to=grog@lemis.com \
--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).