I've just gotten bitten a few times by versions of
APR and 2.0 getting out of sync (i.e. the deprecated
interface removal and the FNM_PERIOD to APR_FNM_PERIOD
rename).

Does our 2.0 ./configure check (or know) in any way
the version (range/minumum) of APR it expects to be
in place ? Or are there fundamental reasons why this
is not possible ?


Dw

Reply via email to