> Under NT you can go to http://www.opensa.org/ and get Apache, mod_ssl,
> OpenSSL and PHP4 with a comfortable installation for about 3MB.
> Five to ten minutes download plus two minutes installation and that`s
> it. That should be ok ?!
I know OpenSA, and I'm even subscribed to its mailing list.
> In any case, last time I installed mod_ssl on an NT, I was forced to
> download and install zillion of other things: Apache (of course...),
> OpenSSL, perl (to run configure.bat), patch.exe (which is used by
> configure.bat), etc., etc. I would be grateful if I could download a
> big (if you ins
[EMAIL PROTECTED] wrote:
>
> > My final vision is to have an integrated source tree, including sub
> > trees for Apache (including EAPI patches), PHP4, JServ (Jakarta?),
> > Perl, OpenSSL, mod_perl, etc., with one simple command (like the
> > "src/helpers/binbuild.sh"), that will build everything
> My final vision is to have an integrated source tree, including sub
> trees for Apache (including EAPI patches), PHP4, JServ (Jakarta?),
> Perl, OpenSSL, mod_perl, etc., with one simple command (like the
> "src/helpers/binbuild.sh"), that will build everything, without an
> installation process
I just re-read Cliff's message, and learned that his meaning was not
what I thought before, after a (too) quick reading of it. So my
response is not too much relevant.
Sorry,
--
Eli Marmor
__
Apache Interface to OpenSSL (mod_ssl
After a long investigation, I found only one real conflict between
UNIX and Windows: src/modules/ssl/Makefile. The Windows version is
copied from Makefile.win32 during the mod_ssl patching procedure,
while the UNIX one is generated automatically during the make of
Apache. To avoid cases in which W
The answer is very simple. All the modules you mentioned (e.g. PHP)
are separate modules. They can (and should) be built out of the
tree of Apache. Even if you choose to build them in the source tree
of Apache, you should do it at least in the separate directory
"src/modules/extra", or by putting
