Nope, I just checked the log files. Building without BDB gives:
START: locks-test
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 1: lock only
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 2: lookup lock by path
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 3: attach lock
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 4: get locks
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 5: basic locking
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 6: test that locking requires proper credentials
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 7: test that locking is enforced in final commit step
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 8: dir propchange can be committed with locked child
svn: Failed to load module for FS type 'bdb'
XFAIL: lt-locks-test 9: able to reserve a name (lock non-existent path)
svn: Failed to load module for FS type 'bdb'
XFAIL: lt-locks-test 10: directory locks (kinda)
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 11: test that locks can expire
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 12: breaking, stealing, refreshing a lock
svn: Failed to load module for FS type 'bdb'
FAIL: lt-locks-test 13: check out-of-dateness before locking
END: locks-test
Looks like it is still trying to access BDB even though it was configured
with "--without-berkeley-db" option.
Any ideas?
--
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 1 05:47:14 2005