Subject: bin/396: ld/ld.so (on hp300) pay too much attention to shared library minor numbers
To: None <peter@alice.wonderland.org>
From: Gordon W. Ross <gwr@jericho.mc.com>
List: netbsd-bugs
Date: 08/08/1994 16:57:41
> From: Peter Galbavy <peter@alice.wonderland.org>
> Date: Sun, 7 Aug 1994 01:14:41 +0100 (BST)

> > I don't know about this.  Aren't minor numbers supposed to be updated 
> > when *new* interfaces are added to a library.  For example, I'll be 
> > adding float versions of most of the math functions to libm soon -- I was 
> > planning to update the minor number from 0 to 1.  Programs linked against
> > 0.0 will still work with 0.1, but those programs that use sinf() or any of
> > the other float math functions won't work with 0.0.

Yes.  Exactly.

> I have to srongly disagree here... Major numbers are updated when any
> part of the interface changes, and minor numbers are updated when there
> are "bug fixes" or non-interface enhancements made to the library.
> 
> Your math library shouls then become 1.0 since the interface has changed.

It should change only when the new interface is not compatible with
the old interface (i.e. old programs would break).  If you just add
new functions, changing the minor number is enough, because programs
demand a minor number that is at least as high as what they were
linked with.  The minor number is not just a "bug-fix" version stamp.

> (At least this is how the rest of the *.so.* world does it :)
No. Not on SunOS, or SVR4 at least.

Gordon W. Ross			  Internet: <gwr@mc.com>
Mercury Computer Systems	Voice mail: 508-256-0052x295
199 Riverneck Road		Front desk: 508-256-1300
Chelmsford, MA 01824-2820	 Facsimile: 508-256-3599

------------------------------------------------------------------------------