Yahoo Groups archive

Milter-greylist

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

Message

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

Attachments

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.