Re: Re: 4.3.4 compile on BIND9 systems
| From: | Melvyn Sopacua | Date: | Mon, 20 Oct 2003 11:41:15 +0000 |
| Subject: | Re: Re: 4.3.4 compile on BIND9 systems | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-4884@lists.php.net to get a copy of this message | ||
On Monday 20 October 2003 13:26, Marko Karppinen wrote:
> On Oct 20, 2003, at 13:06, Jani Taskinen wrote:
> > 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.
>
> I don't think that's true; I think BIND 8 had BIND_4_COMPAT
> and now BIND 9 changed that to BIND_8_COMPAT (seems like
> a pretty boneheaded thing to do, but that's what we have...)
Not really. Jani is right.
The whole compatibility layer is already in the official Bind9 sources and
enabled by default:
/*
* $Id: nameser.h,v 1.2.2.3 2002/07/14 04:26:55 marka Exp $
*/
#ifndef _ARPA_NAMESER_H_
#define _ARPA_NAMESER_H_
#define BIND_4_COMPAT
....
#ifdef BIND_4_COMPAT
#include <arpa/nameser_compat.h>
#endif
Apple devs have re-invented the wheel and made it square. Question is - what
else is triggered with BIND_8_COMPAT in the apple source tree, cause there
must be some alternate reason to do this, other than "There never was a bind4
on apple, so let's rename it".
--
Melvyn