Re: 21.5 Test Suite Failures - database tests

SJT> This could be a configuration problem or a problem in the SJT> tests. I see 10 of 10 tests passed with the Installation SJT> below. SY> I'm wondering if it's a bodgy BerkDB 4.1 install here? Could be. Berk DB 4 support is a user quickie patch, I doubt it's very robust. SJT> Databases: SJT> Compiling in support for Berkeley database. SY> What version? That was 3.2.9. But now I've got 4.1.25 .... SY> Here's my Installation (not the same XEmacs as was used above, SY> but built with the same options/flags and produces the same SY> test errors): OK, you don't specify database, and configure says it detected it. So it's probably either your Berkeley db install or something about v4 we don't properly support yet. I've got Berk DB 4, I think ... ah, but no dev package. Looks like Debian defaults to 3 for dev. Here we go! Jeeeeeeeeez, what lossage! Berk DB 4.1.25 decorates its public API with version information, meaning that you can't do a simple link test! How in the world did you get that far? Or did you disable the decoration? configure.in fragment attached at end ... is this worth doing or should we just let people who don't actually have the right library in place lose? Anyway, it's apparently Berk DB 4.1 losing, because I get ------------------------------------------------------------------------ Testing /playpen/Projects/XEmacs/21.5/tests/automated/database-tests.el... FAIL: Assertion failed: (databasep db) Unexpected error (wrong-type-argument databasep nil) while executing interpreted code. Test suite execution aborted. FAIL: Assertion failed: (databasep db) Unexpected error (wrong-type-argument databasep nil) while executing byte-compiled code. Test suite execution aborted. database-tests.el: 0 of 2 tests successful (0%). Test suite execution failed unexpectedly. ------------------------------------------------------------------------ just like you did. However, I also get ------------------------------------------------------------------------ Testing /playpen/Projects/XEmacs/21.5/tests/automated/symbol-tests.el... symbol-tests.el: 246 of 246 tests successful (100%). ------------------------------------------------------------------------ so your hypothesis about symbol-tests failures being related to Berk DB 4.1 is probably wrong. Here's the Berk DB configure stuff, just for fun (I hope the obscenity checker on Tux doesn't trigger! ;-) ------------------------------------------------------------------------ if test "$with_database_berkdb" != "no"; then AC_MSG_CHECKING(for Berkeley DB version) AC_EGREP_CPP(yes, [#include <$db_h_file> #if DB_VERSION_MAJOR > 1 yes #endif ], [AC_EGREP_CPP(yes, [#include <$db_h_file> #if DB_VERSION_MAJOR > 2 yes #endif ], [AC_EGREP_CPP(yes, [#include <$db_h_file> #if DB_VERSION_MAJOR > 3 yes #endif ], [AC_MSG_RESULT(4); dbfunc=db_create; dbver=4],[ AC_MSG_RESULT(3); dbfunc=db_create; dbver=3])],[ AC_MSG_RESULT(2); dbfunc=db_open; dbver=2])],[ AC_MSG_RESULT(1); dbfunc=dbopen; dbver=1]) AC_CHECK_FUNC($dbfunc, with_database_berkdb=yes need_libdb=no, [ AC_CHECK_LIB(db, $dbfunc, with_database_berkdb=yes need_libdb=yes)]) fi dnl Berk db 4.1 decorates public functions with version information if test "$with_database_berkdb" != "yes" -a "$dbver" = "4"; then rm -f $tempcname echo "#include <$db_h_file>" > $tempcname echo "configure___ dbfunc=db_create" >> $tempcname dnl stolen from above define(TAB, [ ])dnl changequote(, )dnl eval `$CPP -Isrc $tempcname \ | sed -n -e "s/[ TAB]*=[ TAB\"]*/='/" -e "s/[ TAB\"]*\$/'/" -e "s/^configure___//p"` changequote([, ])dnl rm -f $tempcname AC_MSG_WARN("db_create is really $dbfunc") AC_CHECK_LIB(db, $dbfunc, with_database_berkdb=yes need_libdb=yes) fi ------------------------------------------------------------------------ -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.