Bernard Li wrote: > Hi guys: > > Wow... what a long thread... > > IMHO, the best solution here is to look at apache's main loop > implementation and adapt our code. This way, (hopefully) we will get > what we want (late initialization) without modifying any apr code. > Carlo, since you seem to be on a roll here, could you please kindly: > > 1) Take a look at the apache code and see if you can create a working > patch against our source > I believe it has already been observed that examining the Apache code may be no small task - maybe we need to ask someone familiar with Apache
> 2) Engage the apache/apr team to see if they could help us in that regard > I've just posted the issue on d...@apr.apache.org Just another idea: maybe configure can test the supplied apr version to see if the problem exists, and if so, refuse to proceed? Obviously it's not great for BSD users, but at least we could give them a message explaining how to compile a custom apr. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
