Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

missing res_state

missing res_state

2013-10-01 by Bruncsak, Attila

> Here is milter-greylist 4.5.7, which is just 4.5.6 with strndup removed:
> 
> ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-4.5.7.tgz
> MD5 (milter-greylist-4.5.7.tgz) = 1e6a9626792f51cc37aca8a74543c11e
> 
> ChangeLog since 4.5.6:
>         Do not use strndup() for POSIX.1-2001 compatibility
> 

On my system the resolv.h does not contain the following statement:

typedef struct __res_state *res_state;

So I have only __res_state and not res_state.

Does the attached patches break the code for anyone?
If not can it be included into the main stream?

Best,
Attila

Re: [milter-greylist] missing res_state [2 Attachments]

2013-10-01 by manu@...

Bruncsak, Attila <attila.bruncsak@...> wrote:

> On my system the resolv.h does not contain the following statement:
> 
> typedef struct __res_state *res_state;
> 
> So I have only __res_state and not res_state.

You could add an autoconf test to look for res_state, and define a
HAVE_RES_STATE, then:

#ifndef HAVE_RES_STATE
typedef struct __res_state *res_state;
#endif

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

RE: [milter-greylist] missing res_state

2013-10-02 by Bruncsak, Attila

> > On my system the resolv.h does not contain the following statement:
> >
> > typedef struct __res_state *res_state;
> >
> > So I have only __res_state and not res_state.
> 
> You could add an autoconf test to look for res_state, and define a
> HAVE_RES_STATE, then:
> 
> #ifndef HAVE_RES_STATE
> typedef struct __res_state *res_state;
> #endif
> 

I am not an autoconf expert.
May anybody help to write the test for the existence of res_state?

Re: [milter-greylist] missing res_state

2013-10-02 by manu@...

Bruncsak, Attila <attila.bruncsak@...> wrote:

> I am not an autoconf expert.
> May anybody help to write the test for the existence of res_state?

Use existing tests. Add this to configure.ac:
AC_CHECK_TYPE (res_state)

Run autoconf && autoheader && ./configure

config.h should have a HAVE_RES_STATE set or unset, depending whether
configure found it or not. Check config.log to make sure the test did
not fail for a missing header. (you may have to use AC_INCLUDES_DEFAULT
in that case)

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

RE: [milter-greylist] missing res_state

2013-10-07 by Bruncsak, Attila

> > I am not an autoconf expert.
> > May anybody help to write the test for the existence of res_state?
> 
> Use existing tests. Add this to configure.ac:
> AC_CHECK_TYPE (res_state)
> 
> Run autoconf && autoheader && ./configure
> 
> config.h should have a HAVE_RES_STATE set or unset, depending whether
> configure found it or not. Check config.log to make sure the test did
> not fail for a missing header. (you may have to use AC_INCLUDES_DEFAULT
> in that case)
> 

Well, before adding the line
AC_CHECK_TYPE(res_state)
to the configure.ac I tested how the autoconf behaves.
When running autoconf (no modification relative to 4.5.7) I got the following:

configure.ac:94: error: possibly undefined macro: _AC_DEFINE_UNQUOTED
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

Could you advise please?

Re: [milter-greylist] missing res_state

2013-10-07 by Jim Klimov

On 2013-10-07 15:31, Bruncsak, Attila wrote:
> configure.ac:94: error: possibly undefined macro: _AC_DEFINE_UNQUOTED
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.

Possibly, there are several correct answers.

On one hand, I may have been wrong to have used a private(?) -
underscored - interface. I am not an autoconf expert, so I did
what worked for me on several systems I used. If there is a clean
way to rewrite that routine - suggestions are most welcome.
The piece of code in question (used to override header #ifdefs):

m4_define([__AC_UNDEFINE],[_AC_DEFINE_UNQUOTED([#ifdef $1
  #undef $1
#endif])])

On another hand, this routine is part of autoconf and should be
visible to parsed applications. Possibly then, your autoconf is
too old. Is it possible to update it on your system or use some
privately updated build? I guess for your OS it is a replacable
third-party application with few if any OS dependencies.

http://code.metager.de/source/xref/gnu/autoconf/lib/autoconf/general.m4#2164

HTH,
//Jim

Re: [milter-greylist] missing res_state

2013-10-07 by Jim Klimov

On 2013-10-07 19:16, Jim Klimov wrote:
> On 2013-10-07 15:31, Bruncsak, Attila wrote:
>  > configure.ac:94: error: possibly undefined macro: _AC_DEFINE_UNQUOTED
>  > If this token and others are legitimate, please use m4_pattern_allow.
>  > See the Autoconf documentation.
>
> Possibly, there are several correct answers.
>
> On one hand, I may have been wrong to have used a private(?) -
> underscored - interface. I am not an autoconf expert, so I did
> what worked for me on several systems I used. If there is a clean
> way to rewrite that routine - suggestions are most welcome.
> The piece of code in question (used to override header #ifdefs):
>
> m4_define([__AC_UNDEFINE],[_AC_DEFINE_UNQUOTED([#ifdef $1
> #undef $1
> #endif])])
>
> On another hand, this routine is part of autoconf and should be
> visible to parsed applications. Possibly then, your autoconf is
> too old. Is it possible to update it on your system or use some
> privately updated build? I guess for your OS it is a replacable
> third-party application with few if any OS dependencies.
>
> http://code.metager.de/source/xref/gnu/autoconf/lib/autoconf/general.m4#2164

Forgot to add, that as a one-off solution, the modern definitions of
autoconf in general or that routine in particular may be copy-pasted
into your configure.ac.
Show quoted textHide quoted text
>
> HTH,
> //Jim

Re: [milter-greylist] missing res_state

2013-10-08 by manu@...

Bruncsak, Attila <attila.bruncsak@...> wrote:

> configure.ac:94: error: possibly undefined macro: _AC_DEFINE_UNQUOTED
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.

Do you have it defined in a file there?
grep -r _AC_DEFINE_UNQUOTED /usr/share/autoconf/autoconf/



-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

RE: [milter-greylist] missing res_state

2013-10-08 by Bruncsak, Attila

> > configure.ac:94: error: possibly undefined macro: _AC_DEFINE_UNQUOTED
> >       If this token and others are legitimate, please use m4_pattern_allow.
> >       See the Autoconf documentation.
> 
> Do you have it defined in a file there?
> grep -r _AC_DEFINE_UNQUOTED /usr/share/autoconf/autoconf/
> 

No, I do not have if defined.

My autoconf is actually the latest in the CentOS 6 production release. Version information:

autoconf (GNU Autoconf) 2.59
Written by David J. MacKenzie and Akim Demaille.

Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Re: [milter-greylist] missing res_state

2013-10-08 by Jim Klimov

On 2013-10-08 09:47, Bruncsak, Attila wrote:
>  > My autoconf is actually the latest in the CentOS 6 production
> release. Version information:
>  >
>
> Sorry, CentOS 5 release.

Mine on Solaris 10 was installed ages ago (from SunFreeWare ports
when they were still open), and is barely newer than yours:

$ autoconf --version
autoconf (GNU Autoconf) 2.66
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, 
<http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.


I am not sure what is milter-greylist project's policy about supporting
older builds of commonly-available software (which is different from
supporting tweaks for assorted implementations of shells, make's, etc.)

 From what I remember, the GNU auto-stuff was pretty easy to rebuild,
especially on Linux, and you can always install into your own homedir
or another temporary location to avoid conflicts with the OS packaged
version.

Other than that, perhaps updating your installation's general.m4 file
by just copy-pasting the definition would be a more simple solution
(though do back up first!) ;)

//Jim

RE: [milter-greylist] missing res_state

2013-10-08 by Bruncsak, Attila

> >  > My autoconf is actually the latest in the CentOS 6 production
> > release. Version information:
> >  >
> >
> > Sorry, CentOS 5 release.
> 
> Mine on Solaris 10 was installed ages ago (from SunFreeWare ports
> when they were still open), and is barely newer than yours:
> 
> $ autoconf --version
> autoconf (GNU Autoconf) 2.66
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+/Autoconf: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>,
> <http://gnu.org/licenses/exceptions.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by David J. MacKenzie and Akim Demaille.
> 
> 
> I am not sure what is milter-greylist project's policy about supporting
> older builds of commonly-available software (which is different from
> supporting tweaks for assorted implementations of shells, make's, etc.)
> 
>  From what I remember, the GNU auto-stuff was pretty easy to rebuild,
> especially on Linux, and you can always install into your own homedir
> or another temporary location to avoid conflicts with the OS packaged
> version.
> 
> Other than that, perhaps updating your installation's general.m4 file
> by just copy-pasting the definition would be a more simple solution
> (though do back up first!) ;)
> 
> //Jim

So I went ahead and  installed now on CentOS release 6
the autoconf package for testing.
Its version is:

autoconf (GNU Autoconf) 2.63
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

It is not better, since the command
grep -r _AC_DEFINE_UNQUOTED /usr/share/autoconf/autoconf/
still does not found anything.

Of course It is not the bleeding edge Fedora but
we are talking here about the        LATEST       Redhat production Linux distribution !!

I assume we should support it as a compilation environment without much tweaking
of some fancy m4 variables.

Re: [milter-greylist] missing res_state

2013-10-08 by Jim Klimov

On 2013-10-08 11:51, Bruncsak, Attila wrote:
>  > > > My autoconf is actually the latest in the CentOS 6 production
>  > > release. Version information:
>  > > >
>  > >
>  > > Sorry, CentOS 5 release.
>  >
>  > Mine on Solaris 10 was installed ages ago (from SunFreeWare ports
>  > when they were still open), and is barely newer than yours:
>  >
>  > $ autoconf --version
>  > autoconf (GNU Autoconf) 2.66
>  > Copyright (C) 2010 Free Software Foundation, Inc.
>  > License GPLv3+/Autoconf: GNU GPL version 3 or later
>  > <http://gnu.org/licenses/gpl.html>,
>  > <http://gnu.org/licenses/exceptions.html>
>  > This is free software: you are free to change and redistribute it.
>  > There is NO WARRANTY, to the extent permitted by law.
>  >
>  > Written by David J. MacKenzie and Akim Demaille.
>  >
>  >
>  > I am not sure what is milter-greylist project's policy about supporting
>  > older builds of commonly-available software (which is different from
>  > supporting tweaks for assorted implementations of shells, make's, etc.)
>  >
>  > From what I remember, the GNU auto-stuff was pretty easy to rebuild,
>  > especially on Linux, and you can always install into your own homedir
>  > or another temporary location to avoid conflicts with the OS packaged
>  > version.
>  >
>  > Other than that, perhaps updating your installation's general.m4 file
>  > by just copy-pasting the definition would be a more simple solution
>  > (though do back up first!) ;)
>  >
>  > //Jim
>
> So I went ahead and installed now on CentOS release 6
> the autoconf package for testing.
> Its version is:
>
> autoconf (GNU Autoconf) 2.63
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv2+: GNU GPL version 2 or later
> <http://gnu.org/licenses/old-licenses/gpl-2.0.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by David J. MacKenzie and Akim Demaille.
>
> It is not better, since the command
> grep -r _AC_DEFINE_UNQUOTED /usr/share/autoconf/autoconf/
> still does not found anything.
>
> Of course It is not the bleeding edge Fedora but
> we are talking here about the LATEST Redhat production Linux distribution !!
>
> I assume we should support it as a compilation environment without much
> tweaking
> of some fancy m4 variables.

While this is a pretty old version too (hey, 5 years), and might be
said to be the distribution's problem, I do agree now that it is a
problem indeed. I'll see if I have an easy way to tweak or fix this,
other than to "dirtily" copy over the definition into configure.ac.
Or maybe I should do just that? Hopefully, someone with better than
mine understanding of autoconf would step forward now too :)

By the way, in your case - does this discrepancy only break your
ability to re-generate the "configure" script (with autoconf)?
There is no fatal problem such as inability to build the tarball
as-is (which should provide the precompiled version of the script)?

//Jim

Re: [milter-greylist] missing res_state

2013-10-08 by Jim Klimov

Sorry about all the inconvenience, see if this replacement definition
(place into configure.ac:94) would help you?

m4_define([__AC_UNDEFINE],[echo "#ifdef $1
  #undef $1
#endif" >>confdefs.h])


Or in "diff"/"patch" terms, this:

--- 
/home/jim/BuildNew/milter-greylist-buildzone/milter-greylist-cvs-jimbuild/configure.ac 
      2013-09-05 16:26:10.123813858 +0400
+++ configure.ac        2013-10-08 15:59:43.000000000 +0400
@@ -91,9 +91,9 @@
              _FIX_PACKAGE_URL=y
         fi])

-m4_define([__AC_UNDEFINE],[_AC_DEFINE_UNQUOTED([#ifdef $1
+m4_define([__AC_UNDEFINE],[echo "#ifdef $1
   #undef $1
-#endif])])
+#endif" >>confdefs.h])

  if test x"$_FIX_PACKAGE_NAME" = xy; then
      __AC_UNDEFINE([PACKAGE_NAME])

It seems to generate nearly the same shell code via autoconf.

If it works for you, there is a further cleanup patch on this
subject that I'd like to see tested on your system(s) please
(diff against tarball). This is basically the same, except that
it also adds a visible comment about redefinitions, and replaces
repeating double-lines (undef + def) with one routine (redef):

--- 
/home/jim/BuildNew/milter-greylist-buildzone/milter-greylist-cvs-jimbuild/configure.ac 
      2013-09-05 16:26:10.123813858 +0400
+++ configure.ac        2013-10-08 16:25:01.000000000 +0400
@@ -91,30 +91,31 @@
              _FIX_PACKAGE_URL=y
         fi])

-m4_define([__AC_UNDEFINE],[_AC_DEFINE_UNQUOTED([#ifdef $1
+m4_define([__AC_UNDEFINE],[echo "#ifdef $1
   #undef $1
-#endif])])
+#endif" >>confdefs.h])
+
+m4_define([__AC_REDEFINE],[echo \
+               "Redefining macro: '$1' into value '$2'; comment: '$3'"
+    __AC_UNDEFINE([$1])
+    AC_DEFINE_UNQUOTED([$1], [$2], [$3])
+])

  if test x"$_FIX_PACKAGE_NAME" = xy; then
-    __AC_UNDEFINE([PACKAGE_NAME])
-    AC_DEFINE_UNQUOTED([PACKAGE_NAME], ["$PACKAGE_NAME"], [Packaging 
metadata: distro source code name])
+    __AC_REDEFINE([PACKAGE_NAME], ["$PACKAGE_NAME"], [Packaging 
metadata: distro source code name])
  fi

  if test x"$_FIX_PACKAGE_VERSION" = xy; then
-    __AC_UNDEFINE([PACKAGE_VERSION])
-    AC_DEFINE_UNQUOTED([PACKAGE_VERSION], ["$PACKAGE_VERSION"], 
[Packaging metadata: distro source code version])
+    __AC_REDEFINE([PACKAGE_VERSION], ["$PACKAGE_VERSION"], [Packaging 
metadata: distro source code version])
  fi
  if test x"$_FIX_PACKAGE_STRING" = xy; then
-    __AC_UNDEFINE([PACKAGE_STRING])
-    AC_DEFINE_UNQUOTED([PACKAGE_STRING], ["$PACKAGE_STRING"], 
[Packaging metadata: distro source code name+version])
+    __AC_REDEFINE([PACKAGE_STRING], ["$PACKAGE_STRING"], [Packaging 
metadata: distro source code name+version])
  fi
  if test x"$_FIX_PACKAGE_URL" = xy; then
-    __AC_UNDEFINE([PACKAGE_URL])
-    AC_DEFINE_UNQUOTED([PACKAGE_URL], ["$PACKAGE_URL"], [Packaging 
metadata: distro contact])
+    __AC_REDEFINE([PACKAGE_URL], ["$PACKAGE_URL"], [Packaging metadata: 
distro contact])
  fi
  if test x"$_FIX_PACKAGE_BUGREPORT" = xy; then
-    __AC_UNDEFINE([PACKAGE_BUGREPORT])
-    AC_DEFINE_UNQUOTED([PACKAGE_BUGREPORT], ["$PACKAGE_BUGREPORT"], 
[Packaging metadata: distro contact])
+    __AC_REDEFINE([PACKAGE_BUGREPORT], ["$PACKAGE_BUGREPORT"], 
[Packaging metadata: distro contact])
  fi

  AC_DEFINE_UNQUOTED([PACKAGE_VERSION_UPSTREAM], 
["$PACKAGE_VERSION_UPSTREAM"], [Packaging metadata: upstream source code 
version])


   If this works for you, I'd like to submit the latter fix to Manu.

Thanks, and I hope this helps,
//Jim Klimov

RE: [milter-greylist] missing res_state

2013-10-08 by Bruncsak, Attila

> By the way, in your case - does this discrepancy only break your
> ability to re-generate the "configure" script (with autoconf)?
> There is no fatal problem such as inability to build the tarball
> as-is (which should provide the precompiled version of the script)?
> 

If you look at this thread earlier my problem
was just the missing res_state type.
Manu has suggested to make a configure
check for that with autoconf.

Re: [milter-greylist] missing res_state

2013-10-08 by Jim Klimov

On 2013-10-08 14:28, Bruncsak, Attila wrote:
>  > By the way, in your case - does this discrepancy only break your
>  > ability to re-generate the "configure" script (with autoconf)?
>  > There is no fatal problem such as inability to build the tarball
>  > as-is (which should provide the precompiled version of the script)?
>  >
>
> If you look at this thread earlier my problem
> was just the missing res_state type.
> Manu has suggested to make a configure
> check for that with autoconf.

Right, my bad, I did see that earlier but forgot :-\
Did you try today's patch? Did it help?

HTH,
//Jim

RE: [milter-greylist] missing res_state

2013-10-08 by Bruncsak, Attila

> Did you try today's patch? Did it help?
> 

Both the two patches are seemingly fine,
I got cleanly the configure script with no errors.

I could run nicely the configure script too.

On the other hand when I tried to compile,
Immediately I got:

milter-greylist.c: In function 'main':
milter-greylist.c:1575: error: 'PACKAGE_URL' undeclared (first use in this function)
milter-greylist.c:1575: error: (Each undeclared identifier is reported only once
milter-greylist.c:1575: error: for each function it appears in.)
milter-greylist.c:1576: error: expected ':' before 'PACKAGE_URL'
milter-greylist.c: In function 'usage':
milter-greylist.c:2024: error: 'PACKAGE_URL' undeclared (first use in this function)
milter-greylist.c:2025: error: expected ':' before 'PACKAGE_URL'
make: *** [milter-greylist.o] Error 1

Re: [milter-greylist] missing res_state

2013-10-08 by Jim Klimov

Weirder and weirder... can you look if this macro is defined (and is
not ultimately undefined without redefinition) in the config.h which
should be generated by your configure script?

RE: [milter-greylist] missing res_state

2013-10-09 by Bruncsak, Attila

> Weirder and weirder... can you look if this macro is defined (and is
> not ultimately undefined without redefinition) in the config.h which
> should be generated by your configure script?

I do not have defined. Actually this is what I have in it:

/* Packaging metadata: distro contact */
/* #undef PACKAGE_URL */

RE: [milter-greylist] missing res_state

2013-10-09 by Bruncsak, Attila

> > Weirder and weirder... can you look if this macro is defined (and is
> > not ultimately undefined without redefinition) in the config.h which
> > should be generated by your configure script?
> 
> I do not have defined. Actually this is what I have in it:
> 
> /* Packaging metadata: distro contact */
> /* #undef PACKAGE_URL */
> 

Actually looking at the code it is valid
the PACKAGE_URL not to be defined.

It is the code in the milter-greylist.c
which should be prepared to properly
handle the case when it is not defined.

Re: [milter-greylist] missing res_state

2013-10-09 by manu@...

Bruncsak, Attila <attila.bruncsak@...> wrote:

> milter-greylist.c: In function 'main':
> milter-greylist.c:1575: error: 'PACKAGE_URL' undeclared (first 
use in this function)
> milter-greylist.c:1575: error: (Each undeclared identifier is reported
 only once
> milter-greylist.c:1575: error: for each function it appears in.)

Please add in milter-greylist.c:
#ifndef PACKAGE_URL
#define PACKAGE_URL ""
#endif PACKAGE_URL

after #include "config.h"

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

RE: [milter-greylist] missing res_state

2013-10-09 by Bruncsak, Attila

> > milter-greylist.c: In function 'main':
> > milter-greylist.c:1575: error: 'PACKAGE_URL' undeclared (first
> use in this function)
> > milter-greylist.c:1575: error: (Each undeclared identifier is reported
>  only once
> > milter-greylist.c:1575: error: for each function it appears in.)
> 
> Please add in milter-greylist.c:
> #ifndef PACKAGE_URL
> #define PACKAGE_URL ""
> #endif PACKAGE_URL
> 
> after #include "config.h"
> 

It all compiles fine with just a warning:
milter-greylist.c:36:8: warning: extra tokens at end of #endif directive

Re: [milter-greylist] missing res_state

2013-10-09 by Jim Klimov

On 2013-10-09 14:03, manu@... wrote:
> Bruncsak, Attila <attila.bruncsak@...> wrote:
>
>  > milter-greylist.c: In function 'main':
>  > milter-greylist.c:1575: error: 'PACKAGE_URL' undeclared (first
> use in this function)
>  > milter-greylist.c:1575: error: (Each undeclared identifier is reported
> only once
>  > milter-greylist.c:1575: error: for each function it appears in.)
>
> Please add in milter-greylist.c:
> #ifndef PACKAGE_URL
> #define PACKAGE_URL ""
> #endif PACKAGE_URL
>
> after #include "config.h"

I see this is already in CVS :) ... unlike the fix for res_state
or my recent fix (preferably the longer one) for the undef-macros
in configure.ac.

As for PACKAGE_URL: wouldn't a reasonable default be the project's
website?

Should the other PACKAGE_* definitions be similarly enforced as well?

//Jim Klimov

Re: [milter-greylist] missing res_state

2013-10-09 by manu@...

Jim Klimov <jimklimov@...> wrote:

> I see this is already in CVS :) ... unlike the fix for res_state
> or my recent fix (preferably the longer one) for the undef-macros
> in configure.ac.

I think I missed that one.

> As for PACKAGE_URL: wouldn't a reasonable default be the project's
> website? 
> Should the other PACKAGE_* definitions be similarly enforced as well?

Keep it simple, we just need to build the thing.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

RE: [milter-greylist] missing res_state

2013-10-15 by Bruncsak, Attila

> > May anybody help to write the test for the existence of res_state?
> 
> Use existing tests. Add this to configure.ac:
> AC_CHECK_TYPE (res_state)
> 
> Run autoconf && autoheader && ./configure
> 
> config.h should have a HAVE_RES_STATE set or unset, depending whether
> configure found it or not. Check config.log to make sure the test did
> not fail for a missing header. (you may have to use AC_INCLUDES_DEFAULT
> in that case)
> 

Thanks for the help.
Here are the patches.
Is it possible to include them into the next development release please?

--- configure.ac.orig	2013-10-08 16:08:10.000000000 +0200
+++ configure.ac	2013-10-15 09:09:59.000000000 +0200
@@ -475,6 +475,14 @@
 AC_TYPE_SIZE_T
 AC_HEADER_TIME
 
+# Do we have res_state type? Tru64 UNIX doesn't have...
+AC_CHECK_TYPES([res_state],[],[],[
+		#include <sys/types.h>
+		#include <netinet/in.h>
+		#include <arpa/nameser.h>
+		#include <resolv.h>
+])
+
 # Do we need -lpthread with -lbind?
 if test $use_libbind = yes ; then
 	AC_MSG_CHECKING([if -lbind needs -lpthread to link])




--- nsupdate.h.orig	2013-05-19 07:53:34.000000000 +0200
+++ nsupdate.h	2013-10-15 09:17:42.000000000 +0200
@@ -37,6 +37,10 @@
 
 #include "acl.h"
 
+#ifndef HAVE_RES_STATE
+typedef struct __res_state *res_state;
+#endif
+
 void nsupdate_init(void);
 
 struct tsig_entry {



Best,
Attila

Re: [milter-greylist] missing res_state

2013-10-15 by Emmanuel Dreyfus

On Tue, Oct 15, 2013 at 07:32:45AM +0000, Bruncsak, Attila wrote:
> Here are the patches.
> Is it possible to include them into the next development release please?

It is in CVS now.


-- 
Emmanuel Dreyfus
manu@...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.