3 messages in net.sourceforge.lists.courier-maildrop[maildropl] Problem compiling maildro...
FromSent OnAttachments
Bill TomlinsonJun 8, 2005 7:25 am 
Sam VarshavchikJun 8, 2005 7:53 am 
Bill TomlinsonJun 8, 2005 8:27 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Problem compiling maildrop with authlib supportActions...
From:Bill Tomlinson (btom@rndsti.com)
Date:Jun 8, 2005 7:25:33 am
List:net.sourceforge.lists.courier-maildrop

I'm compiling maildrop (v1.8.1) from source and I'm unable to get it to compile with courier authlib support.

I've already compiled authlib (v0.56) from source. The authlib compile was clean. I installed it in the default location (/usr/local) and it works (authtest retrieves data from my LDAP server).

Maildrop compiles cleanly as well, and works (using it's built in authorization, I presume), but it doesn't have authlib support. The configure step always puts "#define AUTHLIB 0" in maildrop/config.h regardless of the various configuration options I've tried.

The INSTALL file says: "If the configure script detects that the Courier Authentication Library is installed, support for courier-authlib gets automatically compiled." But I can't figure out how it is meant to detect authlib. Can anyone explain that detection mechanism?

Now, it's certainly possible that the problem is in my system configuration and not maildrop. For example, I thought that the library lookup path is missing something. So I have tried various options to configure like LDFLAGS, but I haven't found a combination that works (if this is the cause).

Any suggestions would be appreciated.