On Wed, Jan 23, 2013 at 09:51:08AM -0500, Jeffrey Walton wrote:
> Binary compatibility can be tricky, and it brings up all the old
> wounds of Microsoft's COM. Are you claiming there is binary
> compatibility among tool vendors? For example, can I build the base
> with GCC, and then build patches with ICC?
C compilers must adhere to the platform ABI calling conventions.
The same C code generates binary compatible results regardless of
compiler. In particular, shared libraries can be built with any
reasonable C compiler.
> How about different
> versions of the same tool chain (GCC 4.6 and 4.7)? This type of
> interoperability caused a lot of problems in the past.
Not a problem, for example, GCC built shared objects have been
binary compatible with SunPro C shared objects for two decades.
> I tend to agree with Ken and just perform the re-compile. Its not
> worth the aggravation.
What you do is of course up to you, but the OpenSSL ABI is supposed
to stable across patches, and perhaps (but I don't recall the exact
statement) even across micro feature versions. IIRC the ABI changes
with minor versions 1.1.x for example may not be the same ABI as
1.0.x.
Since the OP asked a question, he deserves a factual answer.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
