Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!icdoc!qmw-cs!liam
From: liam@cs.qmw.ac.uk (William Roberts;)
Newsgroups: comp.unix.aux
Subject: Re: 2.0.1 update error
Message-ID: <3072@redstar.cs.qmw.ac.uk>
Date: 30 Apr 91 13:31:55 GMT
References: <-2.++F-@smurf.sub.org> <1171@creatures.cs.vt.edu>
Sender: usenet@cs.qmw.ac.uk
Lines: 25
Nntp-Posting-Host: whitesand.dcs.qmw.ac.uk

In <52157@apple.Apple.COM> antonio@Apple.COM (Antonio Ordonez) writes:

>I didn't want to get involved in this but, the file libc1_s was not part 
>of A/UX 2.0. A/UX 2.0 only included libc_s and libmac_s. The upgrade
>package was intended to upgrade 2.0 systems to 2.0.1.

Perhaps you (or someone else) could clarify this a bit. The questions are:

1) Can A/UX 2.0 binaries complied with -lc_s or -lmac_s be used under
   the CD-ROM distribution of A/UX 2.0.1?

2) Can A/UX 2.0.1 binaries compiled with lc_s or -lmac_s be used with 
   the original A/UX 2.0 distribution?

3) If either compatibility mode fails, how can we use something like "find" to
   identify all the out-of-date binaries?

What changed? Weren't shared libraries intended (at least in part) to permit 
upgrades to the library without breaking existing binaries?
--

William Roberts                 Internet:  liam@dcs.qmw.ac.uk
Queen Mary & Westfield College  UUCP:      liam@qmw-dcs.UUCP
Mile End Road                   AppleLink: UK0087
LONDON, E1 4NS, UK              Tel:  +44 71-975 5234 (Fax: +44 81-980 6533)