[EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] wrote: >> [EMAIL PROTECTED] writes: >>> Specifically, the workaround is to compile the code with the upstream >>> libtool instead of with Debian's libtool, since upstream libtool >>> imports all module symbols into the global namespace. Debian's >>> libtool has been modified to not do this because it causes all sorts >>> of other problems in the general case, but not doing this breaks the >>> meta backend because it wants to reference symbols from the bdb >>> backend. >> s/bdb/ldap/. Sounds like a fix would be to build back-ldap statically >> instead of dynamically on Debian if back-meta is built too. > > The reason back-meta uses code from back-ldap is that they share a lot > of features. Probably, they could be moved into slapd, since they might > be useful in other (proxy-related) future modules? That would be a lot > of reworking, though.
For now we should move those calls into a bi_extra table, the same way back-monitor was handled. But this is stuff for ITS#5355. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
