[csw-maintainers] Symbol versioning for openssl ?

[Yann Rouillard]

>
> Yes, its works at the symbol level but:
>   - the linker doesn't seem to use that information when it links a given
> symbol, it only uses it to check wether or not it can load a library,
>   - it is not registered at the symbol level in the solaris elf file (that
> could perfectly work without it, but it seems that the version is stored
> for each symbol in Linux elf files).
>

Seems I was wrong on the last point. Solaris definitely stores the version
for each symbol. You can get the information through pvs:

# pvs -ors /opt/csw/lib/libneon.so.27.2.6
[...]
/opt/csw/lib/libneon.so.27.2.6 -        libssl.so.0.9.8 (OPENSSL_0.9.8):
SSL_set_ex_data;
/opt/csw/lib/libneon.so.27.2.6 -        libssl.so.0.9.8 (OPENSSL_0.9.8):
SSL_write;
/opt/csw/lib/libneon.so.27.2.6 -        libssl.so.0.9.8 (OPENSSL_0.9.8):
SSL_load_error_strings;
/opt/csw/lib/libneon.so.27.2.6 -        libssl.so.0.9.8 (OPENSSL_0.9.8):
SSL_accept;
/opt/csw/lib/libneon.so.27.2.6 -        libssl.so.0.9.8 (OPENSSL_0.9.8):
SSL_new;
[...]

I am very surprised that the linker doesn't use that information at runtime
to link the symbol.

Yann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20120723/b3919229/attachment.html>