Re: ch_free symbol undefined while loading dynamic backend

[Edward Rudd <eddie@omegaware.com>]

On Sat, 2005-03-05 at 17:48, Howard Chu wrote:
> Edward Rudd wrote:
> 
[snip]

> >
> >Any ideas as to why it is giving this symbol error?  the ITS report just
> >said that the ch_free error *shouldn't happen*, but no solution to fix
> >it, or why it might happen.
> >  
> >
> As noted in the ITS, there is a problem in the build environment. Not 
> enough information was present in the ITS to identify the problem in the 
> environment. In your case, it looks like you're linking with MIT 
> Kerberos, which is certainly a bad idea. OpenLDAP 2.2.23 doesn't support 
> the kpasswd option, so I don't see any reason to link Kerberos here at 
> all. Most notably missing from the ldd output of your back_bdb module is 
> a reference to libdb. In my stock OpenLDAP 2.2.23 build tree this is 
> what I get:
> ldd back-bdb/.libs/back_bdb.so
>         libdb-4.2.so => /usr/local/lib/libdb-4.2.so (0x0000002a95693000)
>         libldap_r-2.2-releng.so.7 => 
> /home/hyc/OD/o22/libraries/libldap_r/.libs/libldap_r-2.2-releng.so.7 
> (0x0000002a95856000)
>         liblber-2.2-releng.so.7 => 
> /home/hyc/OD/o22/libraries/liblber/.libs/liblber-2.2-releng.so.7 
> (0x0000002a95995000)
>         libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a95ac5000)
>         libresolv.so.2 => /lib64/libresolv.so.2 (0x0000002a95ce8000)
>         libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x0000002a95dfd000)
>         libssl.so.0.9.7 => /usr/local/lib/libssl.so.0.9.7 
> (0x0000002a95f14000)
>         libcrypto.so.0.9.7 => /usr/local/lib/libcrypto.so.0.9.7 
> (0x0000002a9604d000)
>         /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 
> (0x000000552aaaa000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x0000002a96293000)

Well I am using a statically linked in libdb instead of a dynamic as the
system DB is 4.1.25 and I want to use the db4.2.52 with openldap, so I
build a private BDB with a different namespace (--with-uniquename) in
the build tree and link against that.

> configure was run with
> --enable-dynamic --enable-modules --enable-bdb=mod --enable-hdb=mod
> 
> TLS and SASL are picked up by default, and I always omit switches that 
> are present by default. (That's what defaults are for, after all.)

this is an inherited RPM from the open-it.org project (which was based
on the early RedHat upstream spec file from redhat circa 7.x).  I will
try disabling kerberos (as I'm not using it anyway) and see if that
solves the issue.

-- 
Edward Rudd <eddie@omegaware.com>
Website http://www.outoforder.cc/