On Fri, Sep 11, 2009 at 04:37:11PM -0700, Murray S. Kucherawy <msk_at_cloudmark.com> wrote:
> I have this:
>
> msk_at_insight(opendkim-1.1.0)$ cat /etc/redhat-release
> Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
> msk_at_insight(opendkim-1.1.0)$ uname -a
> Linux insight.corp.cloudmark.com 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 x86_64 x86_64 GNU/Linux
>
> The build is clean there with the change I committed this morning (i.e. it checks for res_mkquery() and dn_expand() individually). The relevant ./configure output is:
>
> checking for library containing res_mkquery... no
> checking for library containing dn_expand... no
>
> ...so it apparently didn't need the second rule anyway, at least on this system.
Sounds to me like it didn't find -lresolv via those checks, but picked
it up elsewhere...? Did you build with unbound, out of curiosity? It
shouldn't make a difference, but it's the only other variable besides
Linux flavor.
Anyway, if this really IS Debian-specific, then there's no need to hold
up a release for it, IMO. People will undoubtedly try to build it there,
but as soon as those issues are worked out, there'll be an "official"
package they can use, and I'm in the habit of maintaining unofficial
ones for prior releases.
--
Mike Markley <mike_at_markley.org>
One Bell System - it sometimes works.
Received on Fri Sep 11 2009 - 23:42:33 PST