os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Correct a false statement made about shlibs.

Browse source 
Shamelessly stollen from an expert source.

Obtained from:	Peter Wemm's email reply to Satoshi
This commit is contained in:
David E. O'Brien 1996-12-10 10:02:48 +00:00
parent 084d1d1403
commit a132f331c4
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=780
1 changed files with 12 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
handbook/policies.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: policies.sgml,v 1.7 1996-12-10 05:54:31 asami Exp $ --> <!-- $Id: policies.sgml,v 1.8 1996-12-10 10:02:48 obrien Exp $ -->
<!-- The FreeBSD Documentation Project --> <!-- The FreeBSD Documentation Project -->
<chapt><heading>Source Tree Guidelines and Policies <chapt><heading>Source Tree Guidelines and Policies
@ -142,7 +142,7 @@ should be added and it should states things like:
<label id="policies:shlib"> <label id="policies:shlib">
</heading> </heading>
<p><em>Contributed by &a.asami; and &a.obrien;. <p><em>Contributed by &a.asami;, &a.peter;, and &a.obrien;.
<newline>9 December 1996.</em></p> <newline>9 December 1996.</em></p>
<p>If you are adding shared library support to a port or other piece <p>If you are adding shared library support to a port or other piece
@ -166,8 +166,16 @@ should be added and it should states things like:
<p>Stick to version numbers of the form major.minor (x.y). Our dynamic <p>Stick to version numbers of the form major.minor (x.y). Our dynamic
linker does not handle version numbers of the form x.y.z well. Any linker does not handle version numbers of the form x.y.z well. Any
version number after the ``y'' is ignored, and cannot be used to version number after the ``y'' (ie. the third digit) is totally ignored
differentiate between two different shared library versions. when comparing shared lib version numbers to decide which library to
link with. Given two shared libraries that differ only in the `micro'
revision, ld.so will link with the higher one. Ie: if you link with
libfoo.so.3.3.3, the linker only records 3.3 in the headers, and will
link with anything starting with libfoo.so.3.(anything >= 3).(highest
available).
<p>Note that ld.so will always use the highest "minor" revision.
Ie: it will use libc.so.2.2 in preference to libc.so.2.0, even if the
program was initially linked with libc.so.2.0.
<p>For non-port libraries, it is also our policy to change the <p>For non-port libraries, it is also our policy to change the
shared library version number only once between releases. When shared library version number only once between releases. When