The vms.mar I sent you had a small but important bug. Please try this
one instead.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis
In message <[EMAIL PROTECTED]> on Sun, 1 Dec 2002 01:02:16
+0100 (MET), "[EMAIL PROTECTED] via RT" <[EMAIL PROTECTED]> said:
rt> It seems as if you have answered your own earlier suggestion to me. I
rt> can confirm this. With OPSNSSL_NO_ASM defined true BETA 4 builds, tests
rt> and works with
Hi Richard,
It seems as if you have answered your own earlier suggestion to me. I
can confirm this. With OPSNSSL_NO_ASM defined true BETA 4 builds, tests
and works with WASD OK for me too.
I was working my way back down the BETAs, 4 -> 3 -> 2 ..., looking for
one that would work, when I read y
I'd like to report test failures on Mac OS X 10.2.2. I'm writing up an
article for MacDevCenter.com (an ORA site) on building Apache with
mod_ssl support that includes building OpenSSL. It seems to work just
fine, in general, as long as you don't run the tests. So unless you let
me know how to
Building OpenSSL 0.9.7 beta4 and snap 20021129 on RedHat 8.0 (gcc 3.2 &
glibc 2.3) configured with 'no-asm shared --with-krb5-flavor="MIT"' make
fail with undeclared MAXHOSTNAMELEN in ssltest.c (line 693).
After adding #include build ok and pass all tests
--
Ricardo Ariel Gorosito <[EMAIL PROTE
In message on Sat, 30 Nov 2002 12:31:55 EST,
Jeffrey Altman <[EMAIL PROTECTED]> said:
jaltman> The only thing I have not done yet for VMS is provide default
jaltman> locations for the System-wide and User-specific locations for the
jaltman> storing of CERTS/
C-Kermit can now be built on VMS with OpenSSL/Compaq SSL support.
This provides a TELNET START_TLS, TELNET AUTH SSL, HTTPS client for VMS.
Assuming the FTP functionality and IKSD functionality is implemented
on VMS that would also inherit this support
http://www.kermit-project.org/ckermit.html
[levitte - Fri Nov 29 17:31:16 2002]:
> Another question: have you tried defining the logical name
> OPENSSL_NO_ASM with the value YES before building? If you build it
> that way, it should work. I'm assuming the problem lies in
> [.CRYPTO.BN.ASM]VMS.MAR, and if you can verify that it runs all