Karl Lehenbauer wrote:
> I got a warning loading Rivet with Apache 1.33:
> 
> [Tue Sep 27 16:39:47 2005] [warn] Loaded DSO libexec/apache/
> mod_rivet.so uses plain Apache 1.3 API, this module might crash under 
> EAPI! (please recompile it with -DEAPI)
> 
> No problem recompiling it all EAPI.  My question is, should we just 
> make building it with EAPI the default, or should have the configure 
> script dig whether or not it's needed out of the output of "apxs -q 
> CFLAGS" so that it will work either way?

Having the configure script merge the two sets of CFLAGS would be great,
and IIRC, I was headed that way in the Tcl build code, but it's probably
fraught with danger, as they say, if you do anything more than concat
the two groups of flags.

I've often compiled without EAPI and have never had any problems.

-- 
David N. Welton
- http://www.dedasys.com/davidw/

Linux, Open Source Consulting
- http://www.dedasys.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  • EAPI flag Karl Lehenbauer
    • Re: EAPI flag David N. Welton

Reply via email to