[2153] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: thoughts about shared library build process

daemon@ATHENA.MIT.EDU (tytso@MIT.EDU)
Thu Jan 2 01:50:20 1997

Date: Thu, 2 Jan 1997 01:49:56 -0500
To: tlyu@MIT.EDU
Cc: epeisach@MIT.EDU, tlyu@MIT.EDU, krbdev@MIT.EDU
In-Reply-To: <9612300013.AA10039@tesla-coil.MIT.EDU> (message from Tom Yu on
	Sun, 29 Dec 1996 19:13:37 -0500)
From: tytso@MIT.EDU

   Date: Sun, 29 Dec 1996 19:13:37 -0500
   From: Tom Yu <tlyu@MIT.EDU>

   Does linux not deal with sonames or library names that contain a dot
   in the version number?  My logic here is mostly have libfoo.so.MAJ.MIN
   be the "versioned" library name, which would always get compiled and
   installed, and libfoo.so be a symlink.  Are there any systems where
   this will cause breakage?

Linux makes the assumption that a program compiled with
libfoo.so.MAJ.MIN will also work with libfoo.so.MAJ.MIN+1.  I believe
SunOS and Solaris make similar assumptions.

That is, if you're going to make any changes to the binary interface,
you must bump the major version number.

						- Ted

home help back first fref pref prev next nref lref last post