Yahoo Groups archive

Milter-greylist

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

Message

Re: We need you for autoconf hacking (was: Re: [milter-greylist] memory consumption)

2010-02-21 by Johann E. Klasek

On Sat, Feb 20, 2010 at 09:24:42AM +0100, manu@... wrote:
> Johann E. Klasek <johann@...> wrote:
> 
> > > Is it a right move to remove the test on (__RES >= 19991006)? That one
> > > should be much more reliable than attempting to link a program.
> > 
> > As mentioned before this condition was only a quick hack to
> > cope with environments, where res_n* functions are not based
> > on macros.
> 
> Is it? I thought it was to test for res_n* availability.

My answer was maybe too short: Sure, in case res_ninit is not a macro
the simplyfied asumption from __RES >= 19991006 is, that we have at
least a Bind resolver library and this version seem new enough (Bind 8
...) and that we can hope a threaded version is also available. This
seems to hold at least on Solaris but just for res_ninit(). It does not
help much if we want to know if res_ndestroy exists (Solaris 9 has
res_ndestroy, Solaris 8 has't, but both have the same __RES value ...).

So IMHO it is mandatory to use autoconf for optimal portability.

Johann E. K.

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.