Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!mordor!lll-tis!ames!ucbcad!ucbvax!LBL-RTSG.ARPA!vern%lbl-helios
From: vern%lbl-helios@LBL-RTSG.ARPA (Vern Paxson)
Newsgroups: comp.unix.questions
Subject: HPUX 5.2 archiver
Message-ID: <8710052355.AA03056@lbl-helios>
Date: Mon, 5-Oct-87 19:55:12 EDT
Article-I.D.: lbl-heli.8710052355.AA03056
Posted: Mon Oct  5 19:55:12 1987
Date-Received: Thu, 8-Oct-87 07:01:49 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: vern%lbl-helios.arpa@lbl-rtsg.arpa
Lines: 30

I spent an inordinate amount of time today trying to read on a Sun the
contents of an "ar" archive written on an HP9000.  The problem was that
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     `

This extra '/' is the one character they could have chosen which your
typical ar can't chew on.  I finally managed to get the archive read
on a Eunice machine, renaming the screwy hash files it generated to
what they ought to have been, rebuilding the archive, and moving the
result to the Sun.

Questions:

	1.  Is there an easier way to read the archive?  (Hand-editing
	    resulted in "malformed archive" errors.)
	2.  Is there a rational explanation for the incompatibility?

I anticipate having to do more such transfers in the near future, so
I'd appreciate any sage advice someone might be able to offer.  Thanks.

		Vern

	Vern Paxson				vern@lbl-csam.arpa
	Real Time Systems			ucbvax!lbl-csam.arpa!vern
	Lawrence Berkeley Laboratory		(415) 

G5 Oc-1