Greg Stein <gst...@gmail.com> writes: >>> Should we instead check that Subversion and Apache use the same APR? We >>> could do it by checking that "apxs2 -q APR_CONFIG" matches apr_config >>> found by configure. >> >> The server side needs to match httpd's APR. The client side can be different. >> >> Personally, I say that if you find httpd, then mandate its APR >> throughout the build. It is simplest that way. If somebody wants to >> get crazy and provide two different APRs based on client vs server, >> then let them monkey the configuration.
So I made the change to require that the APR used by Subversion matches the APR used by Apache, and one of the buildbots fails: checking whether Apache's APR is compatible configure's APR... no configure: error: Apache's APR version 1.3.8 doesn't match configure's 1.4.5 This buildbot was building successfully before the change. Should we provide a configure flag to allow such builds? Revert the change? -- Philip
