From: Arpadffy Zoltan <zoltan.arpad...@scientificgames.se>
> >I'm having a good time, even if no one else cares.
>
> I do care.
> I apologize for being silent, but I have been very busy with less open sour=
> ce issues.
I wasn't complaining about you, but there are still some open
questions on this stuff, and feedback from the official OpenSSL folks
has been sparse. Pending mysteries include:
What to do about defining a pointer-sized integer type.
What to do with apparently unused ".com" files:
crypto/des/des-lib.com
crypto/threads/pthreads-vms.com
demos/engines/rsaref/build.com
VMS/test-includes.com
If these things are ever to be used, then they need some serious
updating. (Am I missing some documentation related to that RSA
stuff?)
Why this symlink is in the kit:
apps/md4.c;1 -> ../crypto/md4/md4.c
So far, I've left in the C compiler options to disable some
warnings: "LONGLONGTYPE, LONGLONGSUFX, FOUNDCR". I suspect that
now, with /STANDARD = RELAXED, the first two aren't actually
needed. If the source kit is properly packaged, then the last one
probably isn't either. If these things aren't actually needed,
then why not simplify things by removing them? (I may run the
experiment when I get bored.)
The compiler still emits a couple of %CC-I-QUESTCOMPARE
diagnostics which are caused by time_t and size_t being unsigned
(around here):
if (timeleft.tv_sec < 0)
....................^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression
"timeleft.tv_sec" is being compared with a relational operator to a
constant whose value is not greater than zero. This might not be what
you intended.
at line number 226 in file
IT$DKC0:[UTILITY.SOURCE.OPENSSL.openssl-1_0_0d.crypto.bio]bss_dgram.c;1
if (*outlen <= 0)
............^
%CC-I-QUESTCOMPARE, In this statement, the unsigned expression "*outlen"
is being compared with a relational operator to a constant whose value
is not greater than zero. This might not be what you intended.
at line number 180 in file
IT$DKC0:[UTILITY.SOURCE.OPENSSL.openssl-1_0_0d.engines.ccgost]gost94_keyx.c;1
If these things vary by environment, and I assume that at least
time_t does, then it might be nice to have some "configure" test
to see what's what, and act accordingly.
Having a LINK options file named "VAX_DECC_OPTIONS.OPT" even on a
non-VAX system seems misleading, at best. I also doubt that we
actually need any of this stuff, anyway, on any system where this
stuff can be built:
SYS$SHARE:CMA$OPEN_LIB_SHR/SHARE
SYS$SHARE:CMA$OPEN_RTL/SHARE
Cleaning out all the GNU C and VAX C stuff might be fun, too,
unless there's any evidence that anyone would notice.
There are probably more such items, lost in the mists of time, but these
were easy to find in the old-complaint pile.
> I have tested your changes on IA64 and they work well, indeed.
> It was a bit tricky with the unusual extra "64" parameter for tests and ins=
> tall - but it worked perfect.
Just as you need to specify "64" when you build the stuff, you need
to specify which stuff to test, and which stuff to install. Did you
actually use the resulting libraries or shared images (with their new
names), or did you stop when the tests worked? It'd be nice if someone
else could try the new zlib stuff, too.
> Thank you very much for all effort.
> Hope, Richard will merge them into the code and we'll be lucky to see them =
> in the next release.
I'll be holding my breath. It would be nice, of course, to have a
release actually work properly on VMS when it's released. (0.9.8r was a
pleasant surprise that way, I recently discovered.)
------------------------------------------------------------------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
