[fetchmail]fetchmail 6.2.9-rc3 available

[Jim Correia]

On Sep 19, 2005, at 8:45 PM, Matthias Andree wrote:

>> mxget.c: In function =91getmxrecords=92:
>> mxget.c:64: error: =91HEADER=92 undeclared (first use in this =
function)
>>
>> On Mac OS X 10.4.2 it appears the relevant structure is defined in
>> <arpa/nameser_compat.h>.
>
> Same here on Linux - and it's included from arpa/nameser.h.

FWIW, I read the headers again. On Mac OS X 10.4.2 it is defined in  =20
<arpa/nameser_compat.h> or <arpa_nameser8_compat.h>.

The latter appears to only be included by <apra/nameser.h> if =20
BIND_8_COMPAT us defined.

Adding -DBIND_8_COMPAT to the CFLAGS also seems to solve the problem.

> Could you please check:
>
> 1. if config.h (after running ./configure) #defines =20
> HAVE_ARPA_NAMESER_H?
>    (it might use #undef instead)

/* Define to 1 if you have the <arpa/nameser.h> header file. */
#define HAVE_ARPA_NAMESER_H 1


> 2. if there are suspicious warnings or errors in config.log in the
>    vicinity of arpa/nameser.h checks?

Nothing suspicious:

checking arpa/nameser.h usability... yes
checking arpa/nameser.h presence... yes
checking for arpa/nameser.h... yes

> 3. what config.log contains about res_search

Is this the output you are looking for?

configure:8288: checking for res_search
configure:8345: gcc -o conftest -g -O2   conftest.c  >&5
configure:8351: $? =3D 0
configure:8355: test -z
              || test ! -s conftest.err
configure:8358: $? =3D 0
configure:8361: test -s conftest
configure:8364: $? =3D 0
configure:8376: result: yes

configure:8391: checking for res_search
configure:8479: result: yes
configure:8482: result: using libc's resolver functions
configure:8563: checking for crypt
configure:8620: gcc -o conftest -g -O2   conftest.c  >&5
configure:8626: $? =3D 0
configure:8630: test -z
              || test ! -s conftest.err
configure:8633: $? =3D 0
configure:8636: test -s conftest
configure:8639: $? =3D 0
configure:8651: result: yes

#define HAVE_RES_SEARCH 1