Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: HPUX 5.2 archiver
Message-ID: <6529@brl-smoke.ARPA>
Date: Wed, 7-Oct-87 21:46:29 EDT
Article-I.D.: brl-smok.6529
Posted: Wed Oct  7 21:46:29 1987
Date-Received: Sat, 10-Oct-87 12:49:10 EDT
References: <8710052355.AA03056@lbl-helios>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 17

In article <8710052355.AA03056@lbl-helios> vern%lbl-helios.arpa@lbl-rtsg.arpa writes:
>ar on the HP generates non-standard archive headers.  Instead of a line like:
>	nlatt.f         560040370   204   20    100666  83836     `
>it generates
>
>	nlatt.f/        560040370   204   20    100666  83836     `

The H-P "ar" appears to be working right.  This is correct format for the
System V version of "ar".  The problem with the Berkeley version is that
it couldn't handle embedded spaces in member names.  It is possible (and
easy) to make a single "ar" accept both forms of input archive; fix the
one on your Sun to do that.

The other difference between the two flavors of "ar" is that the System V
object module table of contents has a different name and format and is
automatically brought up to date by "ar" when an object member is updated
(no more "ranlib", hooray!).