A little more investigation revealed that BIND_8_COMPAT is some
Apple invention. The official BIND sources have BIND_4_COMPAT,
which is the correct one. Try search with Google for BIND_8_COMPAT
and then BIND_4_COMPAT for some references.
Then go and report bug to Apple folks. :)
--Jani
On Mon, 20 Oct 2003, Jani Taskinen wrote:
>
> I would guess nobody should be using anything older than BIND 8?
> So it would make sense to switch to the new symbols and if someone
> gets compile error, it's just their too old BIND version..?
>
> --Jani
>
>
>On Mon, 20 Oct 2003, Marko Karppinen wrote:
>
>>On Oct 17, 2003, at 18:57, Christian Stocker wrote:
>>> I run into the same problem (OS X 10.3). the following patch would fix
>>> it quick&dirty ;)
>>>
>>> shall I commit it?
>>> or should we even define BIND_8_COMPAT always?
>>
>>Well, if nobody is stepping up to do this the "right" way, ie.
>>switching to the new
>>result type symbols introduced with BIND 8, you should just commit this
>>patch. It at least allows people to compile PHP without tricks on the
>>affected
>>systems.
>>
>
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
