Hello,
I have checked both the 1.0.0 and 0.9.8 20100414 snapshots and it look
much-much better.
Thank you very much Richard and Steven.
I got almost clean compile in both branches
On OPENSSL-098-STABLE-SNAP-20100414 got the following informational message and
a warning.
bss_dgram.c
if (timeleft.tv_sec < 0)
....................^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression
"timeleft.tv_sec" is being compared with a relational op
erator to a constant whose value is not greater than zero. This might not be
what you intended.
at line number 220 in file
USRDSK:[ZAY.WORK.OPENSSL-098-STABLE-SNAP-20100414.CRYPTO.BIO]BSS_DGRAM.C;1
-------------------------------------------------------------------
d1_both.c
item = pqueue_find(s->d1->buffered_messages, seq64be);
.....................................................^
%CC-W-CVTDIFTYPES, In this statement, "seq64be" of type "pointer to unsigned
char", is being converted to "unsigned lon
g long".
at line number 623 in file
USRDSK:[ZAY.WORK.OPENSSL-098-STABLE-SNAP-20100414.SSL]D1_BOTH.C;1
item = pitem_new(seq64be, frag);
.................................^
%CC-W-CVTDIFTYPES, In this statement, "seq64be" of type "pointer to unsigned
char", is being converted to "unsigned lon
g long".
at line number 679 in file
USRDSK:[ZAY.WORK.OPENSSL-098-STABLE-SNAP-20100414.SSL]D1_BOTH.C;1
%LIBRAR-W-COMCOD, compilation warnings in module D1_BOTH file
USRDSK:[ZAY.WORK.OPENSSL-098-STABLE-SNAP-20100414.IA64.OB
J.SSL]D1_BOTH.OBJ;1
-------------------------------------------------------------------------
On OPENSSL-100-STABLE-SNAP-20100414 got just the informational message. No harm
to keep it... but it improves the code if we fix it.
bss_dgram.c
if (timeleft.tv_sec < 0)
....................^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression
"timeleft.tv_sec" is being compared with a relational op
erator to a constant whose value is not greater than zero. This might not be
what you intended.
at line number 226 in file
USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.CRYPTO.BIO]BSS_DGRAM.C;1
---------------------------------------------------------------------
>From other side the tests went fine as well, except that the SSLROOT
>environment variable is not set correctly from the TESTS.COM causeing the
>following error:
Testing key generation with NIST Binary-Curve B-571 .... ok
cat
2071080376:error:02001006:system library:fopen:no such device or
address:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100
414.CRYPTO.BIO]BSS_FILE.C;1:126:fopen('SSLROOT:[000000]openssl.cnf','r')
2071080376:error:2006D002:BIO routines:BIO_new_file:system
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.CRYPTO
.BIO]BSS_FILE.C;1:131:
2071080376:error:0E078002:configuration file routines:DEF_LOAD:system
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-2010
0414.CRYPTO.CONF]CONF_DEF.C;1:199:
2071080376:error:02001006:system library:fopen:no such device or
address:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100
414.CRYPTO.BIO]BSS_FILE.C;1:126:fopen('SSLROOT:[000000]openssl.cnf','r')
2071080376:error:2006D002:BIO routines:BIO_new_file:system
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.CRYPTO
.BIO]BSS_FILE.C;1:131:
2071080376:error:0E078002:configuration file routines:DEF_LOAD:system
lib:USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-2010
0414.CRYPTO.CONF]CONF_DEF.C;1:199:
%BACKUP-E-OPENIN, error opening
USRDSK:[ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.TEST]P.TXT-CLEAR;1 as input
-RMS-E-FNF, file not found
--------------------------------------------------------
...by using a more conventional approach SSLROOT is set correctly and ALL test
PASS happily :)
I have used the following patch in order to make it work.
TITAN2_ZAY $ diff <.test>tests.com;1 <.test>tests.com;5
************
File USRDSK:<ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.TEST>TESTS.COM;1
15 $ sslroot = f$parse("sys$disk:[-.apps];",,,,"syntax_only") -
"].;"+ ".]"
16 $ define /translation_attributes = concealed sslroot 'sslroot'
******
File USRDSK:<ZAY.WORK.OPENSSL-100-STABLE-SNAP-20100414.TEST>TESTS.COM;5
15 $ set default '__here'
16 $ set default [-.apps]
17 $ sslroot = f$parse( f$environment( "default"), , , ,
"no_conceal")
18 $ sslroot = sslroot - "][" - ".000000" - "].;" + ".]"
19 $ define /translation_attributes = concealed sslroot 'sslroot'
************
---------------------------------------------------------------------------
Unfortunately, the install (install.com) do not work at all.
The install directory structure is created, but, except for the include
directory, they are not populated.
Regards,
Z
-----Original Message-----
From: Dr. Stephen Henson [mailto:[email protected]]
Sent: den 13 april 2010 17:03
To: [email protected]
Cc: [email protected]
Subject: Re: OpenSSL 1.0.0a-dev on VMS
On Tue, Apr 13, 2010, Richard Levitte wrote:
> Steven, I've made a number of changes in the 1.0.0 branch, all
> according to what I received from you a couple of weeks ago.
>
> It builds and seems to test fine for me, but I haven't checked
> everything and I'm sure there are things I have missed.
> I'd be happy if you'd be willing to have a look at tomorrow's
> snapshot, which should contain all the changes.
>
> Cheers,
> Richard ( will be on a trip until the end of the week )
>
Please check the 0.9.8 snapshots too.
If there are any minor issues which someone VMS illiterate (i.e. me) can
understand I'll fix them.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
