[Exim] compiling ldap support (again)

Páxina inicial
Borrar esta mensaxe
Responder a esta mensaxe
Autor: Todd Jagger
Data:  
Para: exim-users
Asunto: [Exim] compiling ldap support (again)
Hi,

Trying to compile ldap support in Exim 3.03 on an Irix 6.5
machine. Everything is happy until it gets to the lookups part of
compilation. Then I get:

libident/libident.a pcre/libpcre.a directors/directors.a \
           routers/routers.a transports/transports.a lookups/lookups.a \
           -lelf     \


ld32: ERROR 33: Unresolved text symbol "ldap_is_ldap_url" -- 1st referenced 
by lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_url_parse" -- 1st referenced 
by lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_open" -- 1st referenced by 
lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_free_urldesc" -- 1st 
referenced by lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_bind_s" -- 1st referenced by 
lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_err2string" -- 1st referenced 
by lookups/lookups.a(ldap.o).
         Use linker option -v to see when and which objects, archives and 
dsos are loaded.
ld32: ERROR 33: Unresolved text symbol "ldap_url_search" -- 1st referenced 
by lookups/lookups.a(ldap.o).


(and about another 10 or so lines of similar errors)

I'll admit I'm not sure where to put the -v option to perhaps get some more
useful info about what I've got wrong.

Was hoping that someone here had some spare clue about where I've gone
astray, and better yet, what I might do to fix it.

Thanks,
Todd Jagger