Re: [opendkim-dev] questions on opendkim-1.0.0

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Thu, 27 Aug 2009 07:24:59 -0700 (PDT)

On Thu, 27 Aug 2009, SM wrote:
>> 2. I cannot figure out how can I stop building arlib
>> e.g. configure fails when I run:
>> ./configure --disable-arlib --with-unbound
>
> If you do ./configure --with-unbound, it should not enable arlib. There are
> already some changes in CVS for that. I'll test the --with-unbound option
> again to ensure that it is working correctly.

--disable-arlib was supported by configure but didn't do what you'd expect
in 1.0.0; it would still compile the library but just not use it (i.e. it
would not define USE_ARLIB when compiling other components).

In 1.1.0, it won't even compile unless you specifically request it with
--enable-arlib. By default, the stock resolver is used.

>> 3. I want to set db include path and library path separately.
>> When bdb libraries are installed using FreeBSD ports,
>> they use something like:
>> -I/usr/local/include/db46 -L/usr/local/lib/db46
>
> You can do that through CFLAGS and LDFLAGS. Please post a note if that
> does not work for you.

On the other hand, if it's become common practise to provide configure
options to specify those separately, I guess we should as well. Is that
the case? I note that the NTP package does, for example.

> I'll generate a snapshot of the code from CVS if you want to use it to
> test the above.

Anonymous CVS is also available for getting the latest code. Check
http://sourceforge.net/projects/opendkim for the CVSROOT you need to use.

-MSK
Received on Thu Aug 27 2009 - 14:25:17 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:32:29 PST