[Kolab-devel] OpenLDAP build problem

[Bernhard Herzog]

Steffen Hansen <steffen at klaralvdalens-datakonsult.se> writes:

> --- ../openldap.orig/openldap.spec      2005-02-21 18:02:29.000000000 
> +0100
> +++ openldap.spec       2005-05-24 15:21:35.000000000 +0200
> @@ -90,7 +90,7 @@ AutoReqProv:  no
>      #   (2. make sure our Berkeley-DB is picked up first)
>      %{l_shtool} subst \
>          -e 's;ln -s;ln;g' \
> -        -e 's;-ldb42;-ldb;g' \
> +        -e 's;db43;db;g' \
>          -e 's;<db\.h>;"db.h";g' \
>          configure
>  %if "%{with_sasl}" == "yes"
>
> Anyone got a better idea?

Can you force static linking of libdb?  Perhaps by directly giving
/kolab/lib/libdb.a as a linker option?

This seems to be a pretty general problem with Kolab and perhaps OpenPKG
in general.  Practically all libraries that come with OpenPKG are only
built as static libraries (there's only one *.so in /kolab/lib/ and that
looks like some kind of plugin).  So all linking except for system
libraries like libc should probably be done statically.

On our SUSE Linux Enterprise Server 9 test system, some Kolab programs
(clamav, for instance) are linked dynamicall against the system's bz2
library instead of statically with kolab's own.  In this particular case
it doesn't seem to be a problem because the libraries happen to be
exactly the same base version and I guess that bz2 has much better
binary compatibility than the various libdbs.


   Bernhard

-- 
Intevation GmbH                                 http://intevation.de/
Skencil                                           http://skencil.org/
Thuban                                  http://thuban.intevation.org/