While already running OpenSLL, the next logical step for me would be to
install mod_ssl.
I have to admit, right off the bat, that the configure script is awful.
It behaves unlike any other configure script I have encountered. Aside
from patching and installing files, it has hardcoded paths for the
location of items.
I was always under the impression that configure scripts only configured
the installation of the application you were about to install, rather
than patching and installing files (wouldn't that be part of the make?).
Also, the hardcoded paths make it rather difficults to supply paths
other than the expected ones. For example, the --with-apache= directive
actually takes the path supplied, and tacks on /src/include in order to
find httpd.h.
These problems with the configure script make it quite difficult to set
up and make the necessary binaries before actually doing the
installation and without impacting a currently running system. Is this
a known problem that will be addressed, or is this particular problem
not considered a problem after all?
-Rich
--
Richard West
Wesmo Computer Services http://www.wesmo.com
mailto:[EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
