It used to be possible to build with --disable-nts when a sufficiently new OpenSSL wasn't available, but commit 7c8b5fe20 broke that. I'm not sure why cryptographic functions are needed at all with --disable-nts, but even if they are, the compatibility definitions could have been in a single header instead of replicated all over the place. Fred Wright