Chaskiel M Grundman <[EMAIL PROTECTED]> writes: > Russ Allbery <[EMAIL PROTECTED]> wrote:
>> I expect symbol versioning to do what symbol versioning does, namely to >> provide a mechanism for maintaining a stable ABI even when introducing >> new function signatures so that the library ABI doesn't have to be >> changed > You should be aware that symbol versioning does not do this on solaris. > the notion of a library being able to export symbols with the same name > and different versions pointing at different addresses is a gnu LD > extension > (<http://www.linuxshowcase.org/2000/2000papers/papers/browndavid/browndavid_html/>. > section > 4.1 discusses the capabilities of sun and gnu LD. section 4.2 explains > sun's versioning policy, and why they don't need the multiple-versions > capability: once a function is considered 'public', sun never changes its > function signature) Hm, what *is* the use of symbol versioning on Solaris, then? Does it still help with the case where two versions of the same library are loaded into the running process? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
