I've seen the same thing. Fixing it. Unfortunately, it will mean that you will have to pick up a snapshot a little later or wait until the next release.
Cheers, Richard In message <4971adfe.9030...@tibco.com> on Sat, 17 Jan 2009 05:07:58 -0500, Sue Abercrombie <ab...@tibco.com> said: aberz> I am trying to build a recent OpenSSL release (0.9.8j) on OpenVMS (both Integrity Server and Alpha Server hardware platforms). I am having undefined symbol problems. aberz> aberz> The issue occurs both linking applications and also linking the CRYPTO shared image library. The link symbol warnings are: aberz> aberz> %ILINK-W-USEUNDEF, AES_UNWRAP_KEY referenced aberz> %ILINK-W-USEUNDEF, AES_WRAP_KEY referenced aberz> %ILINK-W-USEUNDEF, BN_X931_DERIVE_PRIME_EX referenced aberz> %ILINK-W-USEUNDEF, BN_X931_GENERATE_PRIME_EX referenced aberz> %ILINK-W-USEUNDEF, BN_X931_GENERATE_XPQ referenced aberz> %ILINK-W-USEUNDEF, DES_OPTIONS referenced aberz> %ILINK-W-USEUNDEF, INT_SMIME_WRITE_ASN1 referenced aberz> %ILINK-W-USEUNDEF, OSSL_LIBDES_VERSION referenced *** aberz> %ILINK-W-USEUNDEF, SMIME_CRLF_COPY referenced aberz> %ILINK-W-USEUNDEF, SMIME_READ_ASN1 referenced aberz> %ILINK-W-USEUNDEF, SMIME_TEXT referenced aberz> aberz> The vector references for LIBCRYPTOSHR.EXE are: aberz> aberz> %ILINK-W-USEUNDEFSYMV, AES_UNWRAP_KEY referenced aberz> %ILINK-W-USEUNDEFSYMV, AES_WRAP_KEY referenced aberz> %ILINK-W-USEUNDEFSYMV, BN_OPTIONS referenced *** aberz> %ILINK-W-USEUNDEFSYMV, BN_X931_DERIVE_PRIME_EX aberz> %ILINK-W-USEUNDEFSYMV, BN_X931_GENERATE_PRIME_EX aberz> %ILINK-W-USEUNDEFSYMV, BN_X931_GENERATE_XPQ referenced aberz> %ILINK-W-USEUNDEFSYMV, DES_OPTIONS referenced aberz> %ILINK-W-USEUNDEFSYMV, INT_CRYPTO_SET_DO_DYNLOCK_CALLBACK refer *** aberz> %ILINK-W-USEUNDEFSYMV, INT_SMIME_WRITE_ASN1 referenced aberz> %ILINK-W-USEUNDEFSYMV, SMIME_CRLF_COPY referenced aberz> %ILINK-W-USEUNDEFSYMV, SMIME_READ_ASN1 referenced aberz> %ILINK-W-USEUNDEFSYMV, SMIME_TEXT referenced aberz> aberz> These two lists are not identical, but closely overlap. Asterisks in these lists indicate symbols which appear in only one of the lists. aberz> aberz> I have looked at the header files, and which C source (and header) files include them and in what order. I don't see a problem with the specification of external symbols. aberz> aberz> I am a bit confused by some of what I see in the header files. For example, there [.crypto.des]des_verh. starts with these definitions: aberz> #define DES_version OSSL_DES_version aberz> #define libdes_version OSSL_libdes_version aberz> which define the short names as the long names. I am much more accustomed (particularly on VMS) to #define statements which define long symbol names to be replaced by shorter symbol names. in the case of these two version functions, the ones actually in the C code are the longer versions. And the long version of the second one, OSSL_libdes_version, is one of the undefined symbols. aberz> aberz> I would be most grateful for any guidance anyone can offer on this problem. aberz> aberz> Thanks in advance! aberz> Sue Abercrombie aberz> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
