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.

were defined.

(before SSLeay, maybe?), it's better to have that macro protect
the compatibility header des_old.h.  In the new des.h, let's use
a slightly different protecting macro.

The rationale is that there are application that might include (via
other header files, perhaps) both an old libdes des.h and OpenSSL's
des.h.  Whichever comes first would overshadow the other because of
the clash in protecting macro.  This fix solves that problem.

(Noticed by Nils Larsch)

Submitted by: Bernhard Simon <simon@zid.tuwien.ac.at>
Reviewed by:
PR:

PR: 393

Submitted by: assar@kth.se
Reviewed by:
PR: 390