>>> Well, knowing httpd will simply segfault otherwise, I'd say, refuse >>> static >>> build for Apache < 2.0.51 with a loud bang. >> >> >> >> +1 >> >> but that also means that currently noone can use Apache 2.0.50 or >> lower with static build. But there is nothing we can do about it. > > > Exactly, and since we _know_ that it will explode otherwise, I think it's > reasonable to simply bail out of the configuration if static was specified > and httpd < 2.0.50 (too bad it is an httpd problem we couldn't work around)
yeah, since there is nothing that can be done about it we really have no choice but to require 2.0.51. but at least we know that it can be done with 2.0.51. or at least we can take active steps to make sure that 2.0.51 has everything we need so we can wipe this todo off. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
