Lines Matching refs:an

36 	1. Make interface additions to an existing library
39 	2. Update an interface in an existing library
40 		- remove an existing interface
43 		- move an interface from one library to another
50 	4. Make an entire library obsolete before end-of-life
58 how to generate an executable file or a shared object from a collection of
96 The structure of mapfile-vers is best explained by an example
134 Each of these sections is a version declaration describing an ABI version of
235 4.0 Making interface additions to an existing library
244 The major revision number is incremented whenever an incompatible change is
245 made to an interface.  This could be the case if an API changes so
256 library (which become part of the ABI), an assertion that specifies the size
276 errors) when running an application with older versions of the library.
304 Consequently, the new version number for an update cannot be a minor
307 SUNW_1.3 and Release N+1 had SUNW_1.4, then interfaces added to an update of
310 may have appeared in Update 2).  The micro versions form an inheritance chain
360 Thus when adding a new Public interface to an update release, both the mapfiles
369 5.0 How to update an interface in an existing library
371 5.1 Removing an existing interface
378 To move an interface from one library to (say) libc, the code has to be
384 This is an exception to the immutability of public symbol versions.  See,
391 When merging an entire library into libc, the mapfile is changed to specify
413 This is similar to what's done when adding a Public interface.  Promoting an
421 As an example, if we were modifying libwombat.so.1 and its existing latest
423 ILLUMOS_0.4.  Therefore, whether you wish to promote an existing Private
435 outside the library.  To move an interface from Private to local scope, simply
454 and ILLUMOS_m.n for an existing library (where m.n is the next version; i.e.,
509 7.0 Make an entire library obsolete
513 Use this version name not for specific interfaces but for marking an entire