>Ooh. So close.
Progress continues. In my never-ending quest for fun, I tried
linking an OPENSSL.EXE using the shared images (SSL_*_SHR*.EXE) instead
of the object libraries (SSL_*.OLB), which is something the normal VMS
builders don't do. Naturally, it didn't work. But it was pretty cl
Ooh. So close.
http://antinode.info/ftp/openssl/1_0_0d/openssl-1_0_0d_s3d.zip
Less buggy editions of:
crypto/install-crypto.com
ssl/install-ssl.com
VMS/mkshared.com
SMS.
__
OpenSSL Project
I'm asking this on the developer list because it seems more of a
development practices issue.
In comparing recent tarballs (e.g. 1.0.0a) against the actual CVS contents,
I am seeing that the tarballs are carrying along a lot of files that are
not in CVS. I could understand having some extras from
