PSARC/2008/071 - Including LCMS with Solaris

[James Carlson]

Alan Coopersmith writes:
> James Carlson wrote:
> > Casper.Dik at Sun.COM writes:
> >>> I don't think that intermediate symbolic link does anything useful.
> >>> The linker only records the actual file name (liblcms.so.1.0.16), and
> >>> only uses the ".so" link to find it, so that liblcms.so.1 just
> >>> provides obfuscation.  ;-}
> >> The linker either records the object "SONAME" if it is present; otherwise
> >> it will just record the "libname.so"; it will not go to the trouble of
> >> expanding links.
> >>
> >> So the question is: what will the libraries SONAME be?
> > 
> > OK.  I haven't seen libraries where SONAME is something other than the
> > actual file name ...
> 
> Most libraries using the Linux style three-part version name only record
> the one-part version name as the SONAME, so that binary compatibility only
> breaks on major version bumps.   The three-part version is just extra
> decoration that may provide some people with more details about exactly
> what version is delivered, but makes it harder to deliver a new minor or
> micro release in a Solaris patch.

I'll bet.  It's a little weird, but as long as the SONAME isn't the
long form, that mostly satisfies my question.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677