[mod_python] Must I configure apache first?

But you have to have Apache configured. Things like file locations,
OS-specific headers, etc, are all not there before configuration. I think
the fact that it compiles and works for you with unconfigured Apache is
pure luck.

You should let SSL do its thing, then compile and install mod_python. Or
you can do it the other way around. There shouldn't be any problems with
that.

--
  Gregory (Grisha) Trubetskoy
       grisha at modpython.org

On Fri, 20 Oct 2000 rsalz at caveosystems.com wrote:

> It's not convenient to disable 'make dependencies' I have to do this:
> 	ac_cv_path_MKDEP=/bin/echo ./configure ...flags...
> I'd rather see "--without-mkdep" or some such flag.
> 
> The reason for not wanting mkdep is that it needs ap_config_pool.h or some
> such file, and since I haven't yet configured apache I don't have that file.
> 
> I don't want to configure apache because mod_ssl wants to do some things,
> and doing mod_python apache and mod_ssl is all getting me confused. :)
> (I keep the unconfig'd sources in my CVS tree and do product builds
> from those virgin sources on a couple of platforms.)
> 
> More importantly, I'd rather the mod_python sources were just inserted
> into the Apache tree and built as part of building apache.  I.e., the old
> way.
> 
> thanks.
> 	/r$
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python
>