example) are declared with some extra linkage information.  This
generates a warning when using the function name as a value to a
regular function pointer with the "correct" definition of the
function.  Therefore, use a macro to cast the appropriate function on
VMS.

strings.h according to X/Open.

was made in a certain sequence.  This change restores the earlier
"chain of command".

callbacks, and their prototypes were consistent as they were. These casts
need reversing.

Also, I personally find line breaks during parameter lists (ie a line
ending in a comma) easier to read at a glance than line breaks at the end
of a function call and before a dereference on the return value (ie a line
ending in a closed-bracket followed by a line starting with "->").

OCSP_CRLID_new and OCSP_crlID_new clash on case-insensitive systems.

get a chance to be defined.
Make a batter file name translator (uhm, no, that's not the finished
variant :-)).

get a chance to be defined.

correctly defined.

lots of silly warnings from the compiler.

get a chance to be defined.

variants of stdio.h that define NULL in such a way that it's "unsafe"
to use for function pointer casting.

missed any.

This compiles and runs on Linux, and external applications have no
problems with it.  The definite test will be to build this on VMS.

Mention BN_[pseudo_]rand with top=-1 in CHANGES.

It's still inconsistent - probably better to undo the whole OPENSSL_NO_* thing.

sure they are available in opensslconf.h, by giving them names starting
with "OPENSSL_" to avoid conflicts with other packages and by making
sure e_os2.h will cover all platform-specific cases together with
opensslconf.h.

I've checked fairly well that nothing breaks with this (apart from
external software that will adapt if they have used something like
NO_KRB5), but I can't guarantee it completely, so a review of this
change would be a good thing.