Lines Matching refs:version

65 required to use version 2 syntax. Note that every mapfile using version 2
90 unique version names.
134 Each of these sections is a version declaration describing an ABI version of
138 ABI versions must be constant, that is version ILLUMOS_0.2 in a given
142 version is publicly visible, it may never be removed or have symbols added
149 The private version, however, is special, and describes any private yet
154 version.
157 introducing one version per interface change.  In illumos, unlike Solaris,
160 any pre-existing Public version.
162 The SUNW_*.* names were the Public version names of the library in Solaris.
163 There should be at most one version name for each release of Solaris, with
164 the minor number incremented by one over the previous version.  No changes
174 Each version must inherit all symbols from its preceding version, specified at
175 the ending "}" for each version. The initial public version does not inherit
176 any symbols.  The private version named either "SUNWprivate" for libraries
184 clients of the library.  If there is no private version, these two lines should
185 appear in the first public version.
187 For maintainability, the list of names in each version block should
190 The version 2 mapfile language supports a simple mechanism for conditional
194 a version SUNW_1.1 that always exports a symbol foo, and also exports
222 the ISA-specific names appear.  The version names are the same as those
223 in the common mapfile, but only non-empty version instances are present
228 ISA-specific mapfiles were used with the version 1 mapfile language, which
239 Public interfaces should be added to a new ILLUMOS_ symbol version, with the
240 minor number incremented by one from the current highest version name. If
242 version name must be introduced.
249 version of the library.
252 is added to a library.  Once a version comes to exist in illumos, it is from
259 private version.  No minor number increment is necessary.
262 the library, the private version must be created (with no major.minor
263 version numbers).  It inherits nothing, nothing inherits from it and it
266 If the library already has Private interfaces in a SUNWprivate version, you
267 should use that.  They may have numbered version names like SUNWprivate_m.n
269 version name to version the new interface.  There is no need to introduce a
270 new private version name.  Be careful not to use a lower numbered private
271 version name; doing so can cause runtime errors (as opposed to load time
297 Consequently, the new version number for an update cannot be a minor
299 version between the two releases.  For example, if Release N had version
351 into the next minor version set, SUNW_1.4.
382 new version in libc for the symbol.
399 for that symbol from the mapfile's private version section.
408 existing interface definition.  Private interfaces have the symbol version
412 version.
415 version were ILLUMOS_0.3, any new ABI would be put into a version called
418 successive minor numbered version level) would be the version that it would
443 SYSVABI and SISCD are reserved version names for interfaces listed in the
445 these version names when copying the implementation of standard interfaces to
447 an existing library (where m.n is the next version; i.e., if the
448 last version was ILLUMOS_0.8, then you should version the interfaces with
497 For maintainability, the list of names in each version block should
504 7.1 Introduce SUNWobsolete version
506 Use this version name not for specific interfaces but for marking an entire
507 library as obsolete.  The existing public/private version names are left
508 unchanged, but a new SUNWobsolete version is created with no symbols in it.
510 There is no numbering of this version name.