Issue encountered in Subversion 1.5.3, with the -deps tarball.
The "configure --help" text for the --with-ssl option indicates that it only
enables SSL support in the bundled Neon library. Nothing is said about SSL
being a requirement to build Subversion.
Configuring on a system without OpenSSL, and without any SSL-related
configure-script arguments:
...
checking for stdint.h... yes
checking for unistd.h... yes
checking openssl/opensslv.h usability... no
checking openssl/opensslv.h presence... no
checking for openssl/opensslv.h... no
configure: error: We require OpenSSL; try --with-openssl
configure failed for serf
Configuring on a system without OpenSSL, with --without-ssl:
...
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
Configuring Serf...
configure: error: '--with-openssl requires a path to a directory'
configure failed for serf
Either the help text and documentation need to be updated to reflect the new
status of OpenSSL as a hard build requirement (and OpenSSL would thereby have
to be added to -deps, raising potential export-control issues), or the bundled
Serf library needs to be beaten into submission.
Bug
Major