Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!labrea!decwrl!decvax!ucbvax!ulysses!hector!jss
From: jss@hector.UUCP (Jerry Schwarz)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Shared libraries (Was: Re: Big Programs Hurt Performance)
Message-ID: <3009@ulysses.homer.nj.att.com>
Date: Wed, 23-Sep-87 15:10:36 EDT
Article-I.D.: ulysses.3009
Posted: Wed Sep 23 15:10:36 1987
Date-Received: Sat, 26-Sep-87 04:49:04 EDT
References: <6886@eddie.MIT.EDU) <2501@xanth.UUCP> <2067@sfsup.UUCP> <2903@phri.UUCP>
Sender: daemon@ulysses.homer.nj.att.com
Reply-To: jss@hector (Jerry Schwarz)
Organization: AT&T Bell Labs, Murray Hill
Lines: 14
Xref: mnetor comp.arch:2315 comp.unix.wizards:4436 comp.os.misc:222

In article <2903@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>
>	One thing that has always bothered me about shared libraries (or
>dynamic loading, if you prefer) is the problem of backward compatability.
>It's not too uncommon that a new version of a program comes along, but some
>people still want to use the old version, for whatever reason.  

You have to relink with the unshared version of the old library. My
understanding is that the tools that build a shared library on System
V build an unshared version at the same time. In most circumstances I
would expect the unshared version to be distributed with the shared
version.

Jerry Schwarz