[Date Prev][Date Next]
RE: Problem in configure openldap on Solaris 2.7
At 10:35 AM 9/21/00 -0700, George Lu wrote:
>You are quite right. Useful info is found in config.log. The configure script try to compile a nd link a conftest.c which refers gdbm_open(), but is not find in libgdbm. The problem in my case is that gdbm installation only creates libgdbm.so.2.0.0 in /usr/local/lib, where the compile command uses -lgdbm. After I made symbolic link to libgdbm.so, works.
>However, using db2 has slightly different problem. The configure script finds the right now trys to link to -ldb, and get error for "db_open... no".
>command "nm libdb.a |grep db_open" list only __db_open but not db_open. This will surely cause failure.
>Is this a bug in configure or due to changes in db2 ? I use BerkeleyDB3.1.17 downlowded from Sleepycat.
Note that DB3.1.17 is not db2... if you want DB2, use 2.7.7.
>From: Kurt D. Zeilenga [<mailto:Kurt@OpenLDAP.org>mailto:Kurt@OpenLDAP.org]
>Sent: Wednesday, September 20, 2000 9:15 PM
>To: George Lu
>Subject: Re: Problem in configure openldap on Solaris 2.7
>At 01:40 PM 9/18/00 -0700, George Lu wrote:
>>I tried toconfig openldap-1.2.11 on Solaris 2.7 with command:
>>env ac_cv_func_pthread_create=no ol_cv_kthread_flag=no \
>> ol_cv_pthread_flag=no ol_cv_pthreads_flag=no \
>> ol_cv_thread_flag=no \
>> CPPFLAGS="-I/usr/local/include" \
>> LDFLAGS="-L/usr/local/lib" \
>> ./configure \
>>I got error msg:
>>checking for pthread_mutex_trylock in -lpthread... no
>>checking for pthread_create in -lpthread... yes
>>checking for thread specific errno... yes
>>checking for GDBM library... checking for gdbm_open... no
>>checking for gdbm_open in -lgdbm... 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
>>*** Error code 1
>>make: Fatal error: Command failed for target `config'
>>I also tried Berkeley DB2, got similar error.
>>Any body can help ? Appreciate any response.
>config.log should provide details as to why detection is failing.
>Likely due to poorly set environment variables...