> From: Richard Levitte <[email protected]>
>
> > sms>
> > http://antinode.info/ftp/openssl/1_0_0d/openssl-SNAP-20110321_s1.zip
> >
> > Just to clarify, you used openssl-SNAP-20110321.tar.gz for this?
> > That's a different branch than the one 1.0.0d comes from...
>
> Yes. (Or "openssl-SNAP-20110321^.tar.gz;1", as it's known around here.)
> [...]
> > If you worked on 1.0.0d before and now played with HEAD, it must be
> > confusing. There are some differences...
>
> The relevant stuff all looked familiar enough.
There does seem to be (at least) one significant difference, though,
on a 32-bit (VAX) system:
GIMP $ cc /version
Compaq C V6.4-005 on OpenVMS VAX V7.3
[...]
e_aes.c
typedef long long i64;
........^
%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported
on this platform.
At line number 20 in GIMP$DUA0:[UTILITY.SOURCE.OPENSSL.OPENSSL-S
NAP-20110321.CRYPTO.MODES]MODES_LCL.H;1.
typedef unsigned long long u64;
........^
%CC-E-NOLONGLONG, In this declaration, 64-bit integral types are not supported
on this platform.
At line number 21 in GIMP$DUA0:[UTILITY.SOURCE.OPENSSL.OPENSSL-S
NAP-20110321.CRYPTO.MODES]MODES_LCL.H;1.
GCM128_CONTEXT gcm;
.......................^
%CC-E-INCOMPMEM, The member "gcm" has an incomplete type.
At line number 199 in GIMP$DUA0:[UTILITY.SOURCE.OPENSSL.OPENSSL-
SNAP-20110321.CRYPTO.EVP]E_AES.C;1.
#endif
%VCG-I-NOBJECT, No object file produced.
At line number 462 in GIMP$DUA0:[UTILITY.SOURCE.OPENSSL.OPENSSL-
SNAP-20110321.CRYPTO.EVP]E_AES.C;1.
%VCG-I-SUMMARY, Completed with 3 error(s), 0 warning(s), and
1 informational messages.
[You have to admire the "(s)" in two out of three places, but not the
one where it was wanted. I'll bet that they don't fix it.]
At line number 462 in GIMP$DUA0:[UTILITY.SOURCE.OPENSSL.OPENSSL-
SNAP-20110321.CRYPTO.EVP]E_AES.C;1.
[...]
Followed by the kinds of unpleasant consequences which one might expect
after that.
At first, I thought that this might be all my fault, because I had
disabled some /WARNING = DISABLE stuff, which included "LONGLONGTYPE"
and "LONGLONGSUFX", but "NOLONGLONG" is a different thing, and not so
easy to ignore:
GIMP $ cc ll.c /warn = disable = NOLONGLONG
%CC-I-CANTDISABLE, The message id nolonglong cannot be disabled.
(I was just making sure that ignoring it would be a big mistake, but the
compiler won't permit that big mistake to be made.)
This stuff was not in 1.0.0d. Is this the kind of optional-feature
module which can be omitted from the build on VAX, or is "long
long"-free code available, or are we doomed now (on VAX)?
------------------------------------------------------------------------
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 [email protected]
Automated List Manager [email protected]
