Thanks, I've noticed the same about those long symbols.  There are a
few more things but that's a good start.  If you check one of the
later snapshots, you'll see that I've fixed quite a bit of stuff.

As to the FIPS stuff, I have simply not had the time to look into it.
There's been quite a lot of changes there since last I looked, and I
believe it requires a bit more care than simply compiling the object
files...  But this is good, you're reminding me of something I should
have dealt with.

Cheers,
Richard

In message <498642f0.3060...@tibco.com> on Sun, 01 Feb 2009 19:48:48 -0500, Sue 
Abercrombie <ab...@tibco.com> said:

aberz> Hi, Richard,
aberz> 
aberz> I have been poking about with the openssl-0.9.8j VMS kit.  I found that
aberz> there is one long symbol not included in symhacks.  I have added this
aberz> block below the CRYPTO symbols in symhacks:
aberz> 
aberz> /* **** Hack some long names not included in CRYPTO list **** */
aberz> #undef int_CRYPTO_set_do_dynlock_callback
aberz> #define int_CRYPTO_set_do_dynlock_callback int_CRYPTO_set_do_dynlock_cb
aberz> 
aberz> In [.UTIL]LIBEAY.NUM I replaced this line
aberz>  int_CRYPTO_set_do_dynlock_callback 4057 EXIST:FUNCTION:
aberz> for the long symbol with these two lines
aberz>  int_CRYPTO_set_do_dynlock_callback 4057 EXIST:!VMS:FUNCTION:
aberz>  int_CRYPTO_set_do_dynlock_cb 4057 EXIST:VMS:FUNCTION:
aberz> so that the SYMBOL_VECTOR in the VMS options file uses the hacked symbol.
aberz> 
aberz> I added five modules to the lists in CRYPTO-LIB.COM, which were not
aberz> being compiled and thus whose symbols aren't in the library.  These are
aberz> aes_wrap, asn_mime, bn_opt, bn_x931p, and des_lib.  In each case, I
aberz> appended the module name to the list of modules in the same directory as
aberz> these.
aberz> 
aberz> These changes give me a clean build of the crypto and ssl libraries and 
their applications.
aberz> 
aberz> Trying to add the FIPS modules to LIBCRYPTO, however, is another problem 
entirely.  FIPS is not a valid parameter to MAKEVMS.COM. [.FIPS]FIPS-LIB 
references source modules which do not exist.  The code in FIPS-LIB which 
defines the logical name OPENSSL for including header files does not produce a 
valid directory name.  I can fix the definition of OPENSSL, but I can't provide 
missing source modules.
aberz> 
aberz> My list of missing C source files referenced in FIPS-LIB.COM is
aberz>  [.fips]fips_err_wrapper.c
aberz>  [.fips.sha]fips_sha1dgst.c
aberz>  [.fips.sha]fips_sha256,fips_sha512.c
aberz>  [.fips.des]fips_des_enc.c
aberz>  [.fips.des]fips_set_key.c
aberz>  [.fips.aes]fips_aes_core.c
aberz> 
aberz> I have not tried to identify missing header files.  Difficult in any 
case, and impossible without all of the .c files.
aberz> 
aberz> Questions, comments, recommendations?  Any and all are welcome.
aberz> 
aberz> Cheers!
aberz> Sue Abercrombie
aberz> Senior Architect
aberz> TIBCO Software Inc.
aberz> 
aberz> 
aberz> Richard Levitte wrote:
aberz> > I've seen the same thing.  Fixing it.  Unfortunately, it will mean
aberz> > that you will have to pick up a snapshot a little later or wait until
aberz> > the next release.
aberz> > Cheers,fips_sha1dgst,fips_sha1_selftest,fips_sha256,fips_sha512
aberz> > Richard
aberz> > In message <4971adfe.9030...@tibco.com> on Sat, 17 Jan 2009 05:07:58 
-0500, Sue Abercrombie <ab...@tibco.com> said:
aberz> > 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>  [... snip ...]
aberz> 

-- 
Richard Levitte                         rich...@levitte.org
                                        http://richard.levitte.org/

"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to