and then didn't support it very well.  And that when there already is a
useful variable for exactly this kind of thing; EX_LIBS...

has been performed (and possibly changed), have it depend on Makefile.ssl.

assignment (modulo those I missed) individual statements.

Incidently, it now compiles so much better without _POSIX_C_SOURCE.

defined in DECC$TYPES.H.  If _POSIX_C_SOURCE is defined, certain types do
not get defined (u_char, u_int, ...).  DECC.H gets included by assert.h
and others.  Now, in6.h uses the types u_char, u_int and so on, and gets
included as part of other header inclusions, and will of course fail because
of the missing types.

On the other hand, _XOPEN_SOURCE_EXTENDED is needed to get gethostname()
properly declared...

Solution: define _XOPEN_SOURCE_EXTENDED much later, so DECC$TYPES.H has
a chance to be included *first*, so the otherwise missing types get defined
properly.

Personal: *mumble* *mumble*

${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.

${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.

Linux for example doesn't exhibit this behaviour, but I add "exit 0" to all
potentially affected rules, just to be on the safe side.

Makefiles... I suppose it wasn't tested very much...

0.9.7-stable.

PR: 373

is not expanded if prepended with a $-sign.

insensitive file names, as well as those that do not have symlinks.
Incidently, both these cases apply on DOS/Windows...

- define a HERE variable to indicate where the source tree is (used
  very little right now)
- make more use of copying and making attribute changes to {file}.new,
  and then move it to {file}
- use 'mv -f' to avoid all those questions to the user when the file
  in question doesn't have write attributes for that user.

Don't define macros in terms of asm() when __STRICT_ANSI is defined.

the one to be used to denote local labels in single function scope.
Problem is that SHA uses same label set across functions, therefore I
have to switch back to $ prefix.

warnings.

Reported by: Bernhard Simon.

shared libraries shared.

callbacks

BIO_s_bio.pod.  The most logical is to move everything needed from
BIO_new_bio_pair.pod to BIO_s_bio.pod (including the nice example)
and toss BIO_new_bio_pair.pod.  I hope I got all the info over properly.
PR: 370

since it's both enumerated and explained in BIO_s_connect.pod.
PR: 370

PR: 353

engine work properly even in bad situations.

configured with zlib support).

callbacks) before attempting to lock.

pushed item.  The index is the number of items - 1.  And if a NULL item was
found, actually use it.
Finally, provide a little bit of safety in CRYPTO_lock() by asserting the a
requested dynamic lock really must exist, instead of just being silent about it

were defined.