Re: Re: 4.3.4 compile on BIND9 systems

In message <Pine.LNX.4.53.0310201441350.17273@netphobia.fi> on Mon, Oct 20, 2003 at 02:44:48PM +0300, Jani Taskinen wrote: > We can't start adding some Apple specific shit for PHP already contains OS-specific excrement (including lines that are Linux-specific, Jani, whether it's acknowledged or not). Different systems differ. Is this not one reason why autoconf/automake/libtool exist? If there is some concern that defining BIND_8_COMPAT may conflict with future definitions of that symbol, perhaps you could #if HAVE_ARPA_NAMESER_COMPAT_H #include <arpa/nameser_compat.h> #endif Although it seems unbelievable that BIND_4_COMPAT would been removed from Darwin (must have happened this year?), it sounds like a naming issue only (with no semantics being affected). In message <5.1.0.14.2.20031020152402.034e6e70@127.0.0.1> on Mon, Oct 20, 2003 at 03:25:12PM +0200, Andi Gutmans wrote: > It should be reported but I agree with Marko that PHP should support some > work around in the meanwhile. It always takes vendors some time to fix > their stuff and we should do what's best for our user base which is create > a working version of PHP ASAP. ^^^^^^^^^^^^^^^^^^^^^^^^^^^ I genuinely appreciate that sentiment. It is promising to hear a voice of reason. In message <Pine.LNX.4.53.0310201441350.17273@netphobia.fi> on Mon, Oct 20, 2003 at 02:44:48PM +0300, Jani Taskinen wrote: > stuff that HAS to be standard.. Regardless of BIND9/Darwin issues, PHP 4.3.4RC2 (as is typical of 4.3 versions) fails to compile with a number of "standard", open-source libraries that other software has no problem with. In some (rare?) cases, PHP might not be at fault from a developer's perspective (and it appears BIND9 is one such situation!), yet PHP may very well behave as though it's at fault (from a package maintainer or end-user's point of view).