INN and db 4,6

[The Doctor]

Just when you thought it safe,  db 4.6 bites you in the bullocks!!

Right when compiling the more recent stable WITH db 4.6 I got:

cd storage   && gmake library
gmake[1]: Entering directory `/usr/source/inn-STABLE-20070918/storage'
/usr/bin/gcc -g -O9 -Wall -march=i686 -I../include  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I. -I/usr//include -c -o ovdb/ovdb.o ovdb/ovdb.c
ovdb/ovdb.c: In function `client_connect':
ovdb/ovdb.c:270: warning: implicit declaration of function `strlcpy'
ovdb/ovdb.c: In function `open_db_file':
ovdb/ovdb.c:612: warning: label `t_open_db_file' defined but not used
ovdb/ovdb.c: In function `delete_old_stuff':
ovdb/ovdb.c:1167: warning: label `out' defined but not used
ovdb/ovdb.c: In function `ovdb_open_berkeleydb':
ovdb/ovdb.c:1529: structure has no member named `set_lk_max'
ovdb/ovdb.c: In function `ovdb_open':
ovdb/ovdb.c:1662: warning: label `t_open_groupaliases' defined but not used
ovdb/ovdb.c:1642: warning: label `t_open_groupinfo' defined but not used
gmake[1]: *** [ovdb/ovdb.o] Error 1
gmake[1]: Leaving directory `/usr/source/inn-STABLE-20070918/storage'
gmake: *** [all-storage] Error 2 

Further

gallifrey2.nk.ca//usr/source/inn-STABLE-20070918$ egrep set_lk_max /usr/include/*.h
/usr/include/db.h:      int  (*set_lk_max_lockers) __P((DB_ENV *, u_int32_t));
/usr/include/db.h:      int  (*set_lk_max_locks) __P((DB_ENV *, u_int32_t));
/usr/include/db.h:      int  (*set_lk_max_objects) __P((DB_ENV *, u_int32_t));
/usr/include/db_cxx.h:  virtual int set_lk_max_lockers(u_int32_t);
/usr/include/db_cxx.h:  virtual int set_lk_max_locks(u_int32_t);
/usr/include/db_cxx.h:  virtual int set_lk_max_objects(u_int32_t);

Hence it looks like for db 4.6 we have to use set_lk_max_locks

And can someone check db 4.5 ?

-- 
Member - Liberal International	
This is doctor at nl2k.ab.ca	Ici doctor at nl2k.ab.ca
God, Queen and country! Beware Anti-Christ rising!
Voting Canadians vote anyone but Harper Cronies!!

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.