On Fri, 19 Feb 2010, Mike Markley wrote:
> It still won't build with ldap enabled:
> libtool: link: gcc -std=gnu99 -I/usr/include -g -O2 -o .libs/opendkim-genzone opendkim_genzone-opendkim-db.o opendkim_genzone-opendkim-genzone.o opendkim_genzone-util.o -L/usr/lib ../libopendkim/.libs/libopendkim.so -lresolv /home/madhack/src/opendkim/testrel/opendkim-2.0.0-pre/libar/.libs/libar.so -lssl -lcrypto -ldb -lldap -pthread -Wl,-rpath -Wl,/usr/local/lib
> opendkim_genzone-opendkim-db.o: In function `dkimf_db_saslinteract':
> /home/madhack/src/opendkim/testrel/opendkim-2.0.0-pre/opendkim/opendkim-db.c:223: undefined reference to `dkimf_get_ldap_param'
>
> ... and several more of that same kind. dkimf_get_ldap_param() seems to
> be in opendkim.c, not opendkim-db.c, which isn't linked in to genzone.
> Does it belong in that file or in opendkim-db.c?
I've rearranged how the LDAP stuff is done. Now, any module that uses
opendkim-db.c for database access that might also use LDAP has to push
required authentication parameters into static storage inside
opendkim-db.c before using the functions in there. Previously,
opendkim-db.c would reach into opendkim.c for the LDAP configuration
values it needs, but obviously this won't work for opendkim-genzone since
it doesn't include opendkim.c in its build.
That means opendkim-genzone now takes "-x conffile" just like opendkim
does, though this is only needed if there are LDAP authentication files in
there that are needed for the connection to work.
Make sense?
Received on Sat Feb 20 2010 - 07:33:41 PST
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sat Feb 20 2010 - 14:50:02 PST