environment variable, SHLIB_PATH.  This change makes that possible.

Submitted by Albert Chin-A-Young <china@thewrittenword.com>

Suggested by Albert Chin-A-Young <china@thewrittenword.com>

little-endian MIPS.
Submitted by Ralf Baechle <ralf@uni-koblenz.de>

At the same time, add VMS support for Rijndael.

you should defined _THREAD_SAFE (I found that in an include file, and
that's what everybody tells me) or _THREADSAFE (that's what the gcc
manual says in the FreeBSD-specific section), so I defined both, just
to be safe.

N.B.: This has not been tested at all, that's my next step.

to have the full extension information, so residual shared libraries
can be removed so the applications and test programs do not get linked
against them by mistake...

  - Make note of the expected extension for the shared libraries and
    if there is a need for symbolic links from for example libcrypto.so.0
    to libcrypto.so.0.9.7.  There is extended info in Configure for
    that.

  - Make as few rebuilds of the shared libraries as possible.

  - Still avoid linking the OpenSSL programs with the shared libraries.

  - When installing, install the shared libraries separately from the
    static ones.

to make them...

use an optimization higher than -O.

Submitted by Kevin Steves <ks@hp.se> 3 months ago...

Submitted by NAKAJI Hiroyuki <nakaji@tutrp.tut.ac.jp>

Make sure that Configure will defined DSO_WIN32 for the Win32 targets.  I feel a bit unsure if this should really be done for Mingw32 and CygWin32

libdl just as linux-elf...

configuration only worked with no-asm.

The old code was painfully primitive and couldn't handle
distinct certificates using the same subject name.

The new code performs several tests on a candidate issuer
certificate based on certificate extensions.

It also adds several callbacks to X509_VERIFY_CTX so its
behaviour can be customised.

Unfortunately some hackery was needed to persuade X509_STORE
to tolerate this. This should go away when X509_STORE is
replaced, sometime...

This must have broken something though :-(

symbols for debugging are defined.

requires that you configure again, but you don't want to reenter all
those configuration arguments again.

(like all the digests).  Setting maxmem to 16K seems to give the
compiler enough space to do all the optimization it wants.

"shared" variables on it's own...

libraries even if the "shared" configuration option wasn't chosen.

there's support for building under Linux and True64 (using examples
from the programming manuals), including versioning that is currently
the same as OpenSSL versions but should really be a different series.

With this change, it's up to the users to decide if they want shared
libraries as well as the static ones.  This decision now has to be
done at configuration time (well, not really, those who know what they
do can still do it the same way as before).

The OpenSSL programs (openssl and the test programs) are currently
always linked statically, but this may change in the future in a
configurable manner.  The necessary makefile variables to enable this
are in place.

Also note that I have done absolutely nothing about the Windows target
to get something similar.  On the other hand, DLLs are already the
default there, but without versioning, and I've no idea what the
possibilities for such a thing are there...

  it cope with OpenBSD which doesn't understand "RTLD_NOW".
* Added the dso_scheme config string entry for OpenBSD-x86 to give it
  DSO support.
* 'make update' that has also absorbed some of Steve's mkstack changes
  for the ASN-related macros.

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.

for use with makefile.one)

MT-support for IRIX 6.x and Alpha-Linux

4.1.4 uses libiberty to define strtoul and strerror.

Submitted by: John Jarvie <jjarvie@newsguy.com>

structures and functions for each stack type. The previous behaviour
can be enabled by configuring with the "-DDEBUG_SAFESTACK" option.
This will also cause "make update" (mkdef.pl in particular) to
update the libeay.num and ssleay.num symbol tables with the number of
extra functions DEBUG_SAFESTACK creates.

The way this change works is to accompany each DECLARE_STACK_OF()
macro with a set of "#define"d versions of the sk_##type##_***
functions that ensures all the existing "type-safe" stack calls are
precompiled into the underlying stack calls. The presence or abscence
of the DEBUG_SAFESTACK symbol controls whether this block of
"#define"s or the DECLARE_STACK_OF() macro is taking effect. The
block of "#define"s is in turn generated and maintained by a perl
script (util/mkstack.pl) that encompasses the block with delimiting
C comments. This works in a similar way to the auto-generated error
codes and, like the other such maintenance utilities, is invoked
by the "make update" target.

A long (but mundane) commit will follow this with the results of
"make update" - this will include all the "#define" blocks for
each DECLARE_STACK_OF() statement, along with stripped down
libeay.num and ssleay.num files.

Also, corrects the linux-elf-arm config string, it was previously setting
$des_obj = dlfcn :-)