William A. Rowe, Jr. schrieb:
Rainer Jung wrote:
Hi Bill,
thanks for this. The problem though is not with the test, but if your
compilation environment does not match your runtime environment. In
Henri's case, and also in the case where we provide binaries, the
build environment contains a newer version of 2.2.x httpd header files
than the real runtime version is. That's why we have an additional
configure flag to overwrite the AP_MODULE_MAGIC_AT_LEAST magic to
build a backwards compatible module even if your build environment
contains the newer API.
Without the flag we check against
AP_MODULE_MAGIC_AT_LEAST(20051115,4), which is fine for 2.2.x and
allows to use ap_get_server_banner() for 2.2.4+. The below test in
mod_ftp trunk is AP_MODULE_MAGIC_AT_LEAST(20060905,0), which is
appropriate for trunk.
It's not an issue; because 2.2 builds of the module can't load in 2.0 and
shouldn't be loaded in 2.3-dev, this simply isn't a problem. The flip
occurs within 2.1-dev and we don't target binaries to such users.
Hmmm, I'm talking only about 2.2. The function ap_get_server_banner()
has been added between 2.2.3 and 2.2.4 with an associated minor MMN
bump. So any module build against 2.2.4 using ap_get_server_banner()
shielded by AP_MODULE_MAGIC_AT_LEAST(20051115,4) will not load into
2.2.3, because the symbol ap_get_server_banner can not be resolved. That
was the original issue noticed by Henri.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
