This is especially true when it's part of a '...'.

Remove one ampersand so the compiler may complain less.
Make rand() static so it will not conflict with the C RTL.
Make bug() static too, for good measure.

"standard" refers to the C language, probably there's also some
standard that defines memory.h).

release.

Also, on Alpha, vms.mar is no longer used (it produced a lot of
confusing messages) for BN.  Instead, the assembler part of bn_lcl.h
is used.

Add info about where to get MASM.

Rebuild error files.

single fault:-) Needless to mention that bnbug.c posted couple of days
ago passes as well...

where the new functions are mentioned.

(they don't really exist before version 7), so that solution was toast.
Instead, let's do it the way it's done on Unix, but then remove older
versions of the file.

That new mechanism *may* fail for some unixly formated file spec,
although I wouldn't worry too much about it.

Actually, this should be resolved by using size_t a bit more, but
that'll be for later.

also needed to get around C compilers on VMS that set the symbol limit
to 31 characters.  Bot the macros VMS and __VMS are checked, since
there's no real way to know if e_os.h has been included yet.

system.

CRYPTO_num_locks() instead of CRYPTO_NUM_LOCKS!), and correct all the
inconsistencies with the rest of OpenSSL.

At least, this compiles nicely on Linux using PTHREADS.  I've done no
other tests so far.

Looks like it fails when b is a power of 2, but I never get incorrect
results.

(actually, much more is needed, like a real config script)

Apparently BN_div_recp reports an error for small divisors
(1,2,4,8,40).

I haven't got mismatches so far. If you can, please run the test
program for a few days (nohup divtest >out& or something), and if it
reports a mismatch, post the output.

signed/unsigned stuff in s3_pkt.c)

Submitted by:
Reviewed by:
PR:

PR: