Set AC_BUILT to 1. Also, added @PTHREAD_CFLAGS@ to uaf2john.  It would not link on mingw without this
Wrapped all unistd.h in wrappers.  Made a wrapper for other headers (fcntl.h, etc). Switched to using -std=c99 in MinGW, which eliminates most of the printf formatting issues, BUT which caused some porting issues
The change for krb5 in 41969aec had the side effect LIBS was polluted.
Don't add OpenCL paths if --disable-opencl.  Revert bogus changes for
OpenCL/CUDA vs HAVE_DL and handle it properly in common-gpu.c instead.
I wondered where all crazy libs checks came from. They are OS-specific!
So let's do them only when appropriate.
Silly typo
Reduced this OMP_SCALE a lot. This was taking a LONG time to run even -test=0
Revert the redundant "=1" for -D. Drop a large block of comments
that does not belong in source. Change more 'dnl' to backslashes.
fix memory leak in krb5-23 format
Fix for legacy build issue with LLd
Merge branch 'bleeding-jumbo' of git://github.com/magnumripper/JohnTheRipper into bleeding-jumbo
Use "$(CC)" instead of "gcc" in Makefiles

To allow autoconf builds with CC=clang and legacy builds
(make -f makefile.orig linux-x86-64-clang) if no gcc is installed.

This also makes sure version checks etc use (gcc compatible) clang
instead of gcc for clang builds:

$ gcc -dumpversion
4.8.2

$ clang -dumpversion
4.2.1

$ gcc -dumpmachine
x86_64-redhat-linux

$ clang -dumpmachine
x86_64-redhat-linux-gnu

As a result, o5logon got slower for clang builds.

Before:
$ ../run/john --test --format=o5logon
Benchmarking: o5logon, Oracle O5LOGON protocol [SHA1 AES 32/64 AES-NI]... DONE
Raw:	4929K c/s real, 4929K c/s virtual

After:
$ ../run/john --test --format=o5logon
Benchmarking: o5logon, Oracle O5LOGON protocol [SHA1 AES 32/64 AES-oSSL]... DONE
Raw:	2655K c/s real, 2655K c/s virtual

(64 bit Linux)

Legacy builds (make -s -f Makefile.orig linux-x86-64-clang) still have another issue:
$ ../run/john --test=0 --format=keepass
Testing: KeePass [SHA256 AES 32/64 OpenSSL]... AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
PASS

$ ../run/john --test=1 --format=keepass
Benchmarking: KeePass [SHA256 AES 32/64 OpenSSL]... AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
AES_set_decrypt_key failed in crypt!
...
AES_set_decrypt_key failed in crypt!
DONE
Raw:	198 c/s real, 202 c/s virtual

The "AES_set_decrypt_key failed in crypt!" errors only occur in
about 50% of the test runs.

The 198 c/s is still much faster than the AES 32/64 OpenSSL speed of an
autoconfig clang build.

$ make -s distclean ; CC=clang ./configure && make -s -j 8
...
$ ../run/john --test --format=keepass
Benchmarking: KeePass [SHA256 AES 32/64 OpenSSL]... DONE
Raw:	126 c/s real, 126 c/s virtual
Revert to a somewhat safer krb5 test (hopefully working for MIT
as well as Heimdal now). If we do not even have the krb5_is_thread_safe()
function, disable OpenMP for krb5-18/23 formats to be safe.
Don't try to use HAVE_LIBKRB5 as an aggregate - create a new one.
Merge pull request #625 from frank-dittrich/bleeding-jumbo

Use "$(CC)" instead of "gcc" in Makefiles
some more Makefile changes

for make clean, use the parent's jobserver for subdirectories
redirect some unwanted possible stderr output to /dev/null
Merge pull request #626 from frank-dittrich/bleeding-jumbo

some more Makefile changes
Better Kerberos 5 detection. Detect MKShim and Heimdal.
Add krb5support to list of libs to search for Kerberos 5 functions.
Revert last patch and simply disable krb5-18/23 formats if Heimdal
was found (until we know, and handle, the differences).