Currently, the SConstruct just appends the ssl libraries to the environment when --ssl is specified; there is no configure check.
This means that when you specify the wrong library path or the ssl libraries are missing, you will get strange seemingly-unrelated configure failures, since some of the configure checks depend on the linker working properly. You must then scour config.log to determine the cause of the failure.
- related to
SERVER-18053 Building with the enterprise module should error out if SSL is not enabled