At Wed, 18 May 2011 19:32:25 +0200 (CEST), OpenSSL RT wrote:
> 
> Want to get rid of the error in your builds? Add -Bsymbolic
> too... It's more than appropriate in cases when you embed
> libcrypto.a into another shared library, which [normally] is not
> meant to export OpenSSL symbols. By doing so, you avoid symbol table
> cross contamination and so to say imprison openssl in your shared
> library. Regardless outcome of this discussion I'd recommend [at
> least Rob] to consider doing so.

Very good advice.  Would not have thought of this, as the silent rules
rules in Makefile.shared do such a good job of hiding the grotty
details that I never noticed that they were setting -Wl,-Bsymbolic.

Yes, this seems to suppress the error, at least on the platforms I've
tested so far, and may also remove the need for a related kludge we
had to use on platforms where Python itself is linked against an old
version of OpenSSL.

Thank you!


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to