Investigating on agnesi, I see that this is the failing bit of the test: berkdb_open -create -btree -mode 0644 -env env1 -encrypt a.db
whereas this command immediately before it works fine: berkdb_open -create -btree -mode 0644 -env env0 -auto_commit a.db so it looks like this is a problem with the encryption of some sort? A reduced test case with the same error output is attached. Can be run as: echo "source ../test/test.tcl; run_std env007" | tclsh8.5 How do these tcl commands map to C, for better debugging? Would it make sense to disable encryption support on arm? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED]
env007.tcl
Description: Tcl script
