Is it possible when building courier-authlib to not have it do anything at all with Berkeley db? Before this component was split off from courier, all I had to do is configure with "--with-db=gdbm", and everything used to build fine.
But now, when I configure courier-authlib with "--with-db=gdbm", I get errors in the bdb* routines because things like db_open cannot be found. Is there any way to totally prevent any of this bdb* stuff from getting built in the first place in courier-authlib? Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
