Benjamin Griese wrote:
Hi Prentice,
in general you're right I wouldn't say something if he had a release in the lower 2.4s, but the version he is using is _two major_ releases behind. Probably when he fixed his original problem, its not too far away to think of the next problem due to a bug thats already fixed in a newer version. Thats the only point I was thinking of by saying that.
Not to mention that gdbm was never a safe DB mechanism, it has a lot of thread safety issues. No matter what, sticking with it would be a mistake. And nobody on the Project will support anything that old. We've already dropped support for 2.3 now; if you're not on 2.4 by now then don't bother posting to these lists.
Bye.
On Mon, Oct 18, 2010 at 15:46, Prentice Bisbalprentice@ias.edu wrote:
Benjamin,
Telling someone to upgrade their software just because it's an older version is not an appropriate response. It looks like the configure script can't find the ldbm library, so even if he upgraded to teh latest version, if he doesn't correct his environment, he may still have the same error.
Prentice
Benjamin Griese wrote:
Hello Piotr, you should consider updating your ancient OpenLDAP-Server. :)
Bye, Benjamin.
On Mon, Oct 18, 2010 at 14:14, KALINOWSKI, Piotr (Piotr) piotr.kalinowski@alcatel-lucent.com wrote:
Hello,
I am trying to build OpenLDAP version 2.2.17 with the gdbm back end. The platform is Solaris 10 on SPARC. However, the configure script fails with the following error: ./configure --enable-ldbm --with-ldbm-api=gdbm --enable-shell --enable-crypt --disable-bdb ... checking for GDBM library... checking for gdbm_open... no checking for gdbm_open in -lgdbm... no no checking for gdbm.h... yes checking for db... no configure: warning: could not find suitable LDBM backend configure: error: select appropriate LDBM options or disable Does anyone know how to fix it? Thanks in advance. Piotr