[Pvfs2-developers] bdb.m4 uninitialized variables break default Fedora Core 5 build

Number Cruncher number.cruncher at ntlworld.com
Fri Jan 19 07:53:37 EST 2007


I'm using RPM to simplify installation and can't build pvfs-2.6.2 on FC5 
using the default RPM compiler build flags which include "-Werror" on FC5.

This breaks the configure test for HAVE_TXNID_PARAMETER_TO_DB_OPEN 
because the parameters are used uninitialized. The test fails silently 
but the system installed BDB does require the TXNID parameter which 
breaks the subsequent build:

src/io/trove/trove-dbpf/dbpf-mgmt.c: In function 'dbpf_getdb_env':
src/io/trove/trove-dbpf/dbpf-mgmt.c:98: warning: passing argument 2 of 
'dbenv->set_errcall' from incompatible pointer type
src/io/trove/trove-dbpf/dbpf-mgmt.c: In function 'db_open':
src/io/trove/trove-dbpf/dbpf-mgmt.c:1653: warning: passing argument 2 of 
'db_p->open' from incompatible pointer type
src/io/trove/trove-dbpf/dbpf-mgmt.c:1653: warning: passing argument 4 of 
'db_p->open' makes pointer from integer without a cast
src/io/trove/trove-dbpf/dbpf-mgmt.c:1653: error: too few arguments to 
function 'db_p->open'

Workaround: overwrite default compiler flags.

Fix: initialize variables in pvfs-2.6.2/maint/config/bdb.m4 
HAVE_TXNID_PARAMETER_TO_DB_OPEN macro.


Thanks,
Simon


More information about the Pvfs2-developers mailing list