[Date Prev][Date Next] [Chronological] [Thread] [Top]

Solaris with gdbm LDBM install problem



I tried to follow the directions below to resolve the same error he was
getting but the ONLY file I can find is
/usr/local/lib/libgdbm.a
any help would be greatly appreciated.
##################################
$ uname -a
SunOS netman 5.7 Generic_106541-10 sun4u sparc SUNW,Ultra-5_10
$ env
_=/bin/env
MANPATH=:/usr/share/man:/usr/local/man
_INIT_UTS_RELEASE=5.7
HZ=100
_INIT_UTS_MACHINE=sun4u
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/mysql/bin:/usr/
ccs/bin:/usr/xpg4/bin:/usr/local/BerkeleyDB.3.1/include:/usr/local/BerkeleyD
B.3.1/lib
_INIT_UTS_VERSION=Generic_106541-10
_INIT_RUN_NPREV=0
LOGNAME=chuff
_INIT_UTS_NODENAME=netman
_INIT_UTS_ISA=sparc
MAIL=/usr/mail/chuff
_INIT_PREV_LEVEL=S
SHELL=/usr/bin/sh
HOME=/export/home/chuff
_INIT_UTS_SYSNAME=SunOS
LD_LIBRARY_PATH=:/usr/local/lib
TERM=xterm
PWD=/export/home/chuff/openldap-1.2.11
TZ=US/Eastern
_INIT_RUN_LEVEL=3
_INIT_UTS_PLATFORM=SUNW,Ultra-5_10
$
$ echo $PATH
/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/mysql/bin:/usr/ccs/b
in:/usr/xpg4/bin:
$ tail -20 config.log
configure:6695: checking for gdbm_open in -lgdbm
configure:6714: gcc -o conftest -g -O2 -I/usr/local/include -L/usr/local/lib
conftest.c -lgdbm  -lresolv -lgen -lnsl -lsocket  1>&5
Undefined                       first referenced
 symbol                             in file
gdbm_open                           /var/tmp/ccbpaiqu1.o
ld: fatal: Symbol referencing errors. No output written to conftest
configure: failed program was:
#line 6703 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
    builtin and then its argument prototype would still apply.  */
char gdbm_open();

int main() {
gdbm_open()
; return 0; }
configure:6749: checking for gdbm.h
configure:6759: gcc -E -I/usr/local/include conftest.c >/dev/null
2>conftest.out
configure:6786: checking for db
$


Title: RE: Problem in configure openldap on Solaris 2.7
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. 


-----Original Message----- 
From: Kurt D. Zeilenga [<mailto:Kurt@OpenLDAP.org>] 
Sent: Wednesday, September 20, 2000 9:15 PM 
To: George Lu 
Cc: openldap-software@OpenLDAP.org 
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 \ 
> --with-ldbm-api=gdbm 
> 
>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 
>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...