rand_lcl.h

The message to everyone is "Do not hack OpenSSL when stressed"...

the RANDEGD environment variable.

today.  Time to add extra info so the poor users know where to
go with their troubles.

Fixes for Win32 build.

This is mostly a work around for the old VC++ problem
that it treats func() as func(void).

Various prototypes had been added to 'compare' function
pointers that triggered this. This could be fixed by removing
the prototype, adding function pointer casts to every call or
changing the passed function to use the expected arguments.
I mostly did the latter.

The mkdef.pl script was modified to remove the typesafe
functions which no longer exist.

Oh and some functions called OPENSSL_freeLibrary() were
changed back to FreeLibrary(), wonder how that happened :-)

label. (Reported by Alexei Bakharevski.)

Also, "make update" has added some missing functions to libeay.num,
updated the TABLE for the alpha changes, and updated thousands of
dependancies that have changed from recent commits.

like Malloc, Realloc and especially Free conflict with already existing names
on some operating systems or other packages.  That is reason enough to change
the names of the OpenSSL memory allocation macros to something that has a
better chance of being unique, like prepending them with OPENSSL_.

This change includes all the name changes needed throughout all C files.

They have nothing to do with the particular PRNG (md_rand.c).

This is superfluous now that we don't have to avoid creating
multiple versions of the file on VMS (because older versions
are now deleted).

"Jan Mikkelsen" <janm@transactionsite.com> correctly states that the
OpenSSL header files have #include's and extern "C"'s in an incorrect
order.  Thusly fixed.

variables are locked.

it's a good thing if ssleay_rand_status() would do the corresponding
lock and unlock as everyone else...

on Win32.

couldn't be opened.

strings, it's just the default because it's usually ok.

Submitted by: Andrew Gray <agray@iconsinc.com>

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

(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, much more is needed, like a real config script)

Submitted by: Lutz Jaenicke <Lutz.Jaenicke@aet.TU-Cottbus.DE>

because this will drain the entropy pool.

"make update".