Yann Rouillard <[email protected]> wrote: > > Given the fact that the same mapfiles work on Solaris and Linux, I am not > > convinced that Linux is different. > > > > 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). > > But I may have done something wrong, you could have a look at my previous > email to see the tests I made (I showed the output of pvs to check if the > symbol versioning information was there) and I just commited my > modifications so you can have a look on svn: > - the mapfiles are here: > http://gar.svn.sourceforge.net/viewvc/gar/csw/mgar/pkg/openssl1/trunk/files/map.openssl.engines > , > http://gar.svn.sourceforge.net/viewvc/gar/csw/mgar/pkg/openssl1/trunk/files/map.openssl.libssl > and > http://gar.svn.sourceforge.net/viewvc/gar/csw/mgar/pkg/openssl1/trunk/files/map.openssl.libcrypto
You may like to look at the map file from libschily: ftp://ftp.berlios.de/pub/schily/ You did not use nested definitions. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
