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
272 errors) when running an application with older versions of the library.
297 Consequently, the new version number for an update cannot be a minor
301 an update of Release N must have micro numbers such as SUNW_1.3.1,
304 an inheritance chain that is inserted between two successive minor versions.
353 Thus when adding a new Public interface to an update release, both the mapfiles
362 5.0 How to update an interface in an existing library
364 5.1 Removing an existing interface
371 To move an interface from one library to (say) libc, the code has to be
377 This is an exception to the immutability of public symbol versions. See,
384 When merging an entire library into libc, the mapfile is changed to specify
406 This is similar to what's done when adding a Public interface. Promoting an
414 As an example, if we were modifying libwombat.so.1 and its existing latest
416 ILLUMOS_0.4. Therefore, whether you wish to promote an existing Private
428 outside the library. To move an interface from Private to local scope, simply
447 an existing library (where m.n is the next version; i.e., if the
502 7.0 Make an entire library obsolete
506 Use this version name not for specific interfaces but for marking an entire