hi philip,
>> Exim-4.52 (release) now builds on (my) OSX 10.4.1 as follows:
>
> That's good.
>
>> # ADD the nameser_compat.h include in ONE place ...
>
> That's not good.
>
>> =========================================
>> (EDITOR) /usr/ports/exim/exim-4.52/src/exim.h
>> @49
>> /* ANSI C standard includes */
>> +++ #include <arpa/nameser_compat.h>
>> # include <ctype.h>
>> =========================================
>
> If there really is no CFLAGS setting that can be used to force the
> automatic inclusion of this from arpa/nameser.h, then I will have to
> invent some new parameter than can be set in OS/os.h-Darwin to cause
> this inclusion to happen.
in my limited experience, BIND_8_COMPAT is *supposed* to be the flag that does
the trick ... but i've only seen/used it in configure.in, NOT on the cmd line
...
e.g., in clamav-0.85.1's source:
one finds in 'configure.in':
...
case "$target_os" in
...
darwin*)
AC_DEFINE(C_BSD,1,[os is bsd flavor])
AC_DEFINE(C_DARWIN,1,[os is darwin])
AC_DEFINE(BIND_8_COMPAT,1,[enable bind8 compatibility])
use_netinfo="yes"
disable_gethostbyname_r="yes"
;;
...
and in 'clamav-config.h':
...
cat >>confdefs.h <<\_ACEOF
#define BIND_8_COMPAT 1
_ACEOF
...
without the 'autoconf'-based build sys in/for exim, i am, alas, not certain
where/how best to flag the inclusion ...
there's a thread here
(<
http://mailman.icsi.berkeley.edu/pipermail/bro/2004-July/001521.html>) that
discusses it for BIND9 ... perhaps of interest?
richard
