Otherwise, the test target will fail because libcrypto.sha1 is missing
or not up to date.

that macro.

It's possible that OPENSSL_UNISTD_IO should be used instead of
OPENSSL_UNISTD, for the MSDOS case...

make update.

non-FIPS mode.

Update the appropriate fingerprints accordingly.
(something is weird, someone else was working on the same stuff, and
removed fips_sha1_selftest.c from fips/sha1/standalone.sha1...)

strlen(), memcmp(), exit() and others to be used without a proper
declaration.

Update the appropriate fingerprints accordingly.

weren't due to that, but to a change on the SCO machines I used for
testing, where my $PATH was suddenly incorrect.

  implementations.
- Reorder the build so the standalone FIPS SHA1 checker is built
  first.
- Add necessary defines to avoid symbol clashes between FIPS and
  non-FIPS implementations.
- Change necessary signatures.
- Correct bugs in FIPS build Makefiles.
- make update

0_9_7-stable'.

-DFIPS.  This is basically only visible when building with shared
library supoort...

1. CreateToolhelp32Snapshot returns INVALID_HANDLE_VALUE, not NULL, on error.
2. On Windows CE, a snapshot handle is closed with CloseToolhelp32Snapshot,
   not CloseHandle.

fix typo

(I'm quite worried about what this will do to compatibility with
earlier 0.9.7 versions)

and perhaps the conflict this generates on the person that hasn't yet
committed the real file will prompt him to do so :-).