VMS: Use strict refdef extern model when building library object files
authorRichard Levitte <levitte@openssl.org>
Mon, 22 Aug 2016 08:17:27 +0000 (10:17 +0200)
committerRichard Levitte <levitte@openssl.org>
Mon, 22 Aug 2016 13:50:28 +0000 (15:50 +0200)
commit51690fb8881955a4ff3f4648a06f1be3f0945d7b
tree4d05a4ea3c9b7a1c8ce994d3dea5375399ffcea7
parent93c616d6110d29c513c46d82b2283eb1a9e74dc0
VMS: Use strict refdef extern model when building library object files

Most of the time, this isn't strictly needed.  However, in the default
extern model (called relaxed refdef), symbols are treated as weak
common objects unless they are initialised.  The librarian doesn't
include weak symbols in the (static) libraries, which renders them
invisible when linking a program with said those libraries, which is a
problem at times.

Using the strict refdef model is much more like standard C on all
other platforms, and thereby avoid the issues that come with the
relaxed refdef model.

Note: this doesn't apply to VAX C.  It's possible that this will make
OpenSSL building with VAX C difficult some time in the future if it
isn't already.  However, VAX C is a very old compiler that we don't
expect to see too often, as DEC C (a.k.a VMS C) should have replaced
it a long time ago.

Reviewed-by: Rich Salz <rsalz@openssl.org>
crypto/crypto-lib.com
ssl/ssl-lib.com