[elephant-devel] SBCL errors

[Kevin Raison]

Nikodemus, you can do the following to test the BDB backend, assuming 
that you have the BDB libs installed and your my-config.sexp* setup:

(asdf:operate 'asdf:load-op :elephant)
(asdf:operate 'asdf:load-op :ele-bdb)
(asdf:operate 'asdf:load-op :elephant-tests)
(in-package "ELEPHANT-TESTS")
(setq *default-spec* *testbdb-spec*)
(do-backend-tests)

After each test, you will want to clear out the test repo by changing to 
the elephant tests directory and running a script:

cd /usr/local/lib/sbcl/site/elephant-1.0/tests
sh ./delscript.sh

Cheers,
Kevin


* my-config.sexp goes in the elephant distribution root, in my case 
/usr/local/lib/sbcl/site/elephant-1.0/my-config.sexp.  On Ubuntu 10.04, 
with libdb4.7, libdb4.7-dev and db4.7-util packages installed, 
my-config.sexp should look like:

((:compiler . :gcc)
  (:berkeley-db-version . "4.7")
  (:berkeley-db-include-dir . "/usr/include/")
  (:berkeley-db-lib-dir . "/usr/lib/")
  (:berkeley-db-lib . "/usr/lib/libdb-4.7.so")
  (:berkeley-db-deadlock . "/usr/bin/db4.7_deadlock")
  (:berkeley-db-cachesize . 20971520)
  (:berkeley-db-max-locks . 2000)
  (:berkeley-db-max-objects . 2000)
  (:berkeley-db-max-transactions . 1000)
  (:berkeley-db-map-degree2 . t)
  (:berkeley-db-mvcc . nil)
  (:warn-when-dropping-persistent-slots . nil)
  (:return-null-on-missing-instance . t)
  (:no-deserialization-package-found-action . :warn)
  (:clsql-lib-paths . nil)
  (:prebuilt-libraries . nil))



On 08/23/2011 03:58 AM, Nikodemus Siivola wrote:
> On 23 August 2011 07:54, Kevin Raison<raison at chatsubo.net>  wrote:
>
>> I just pulled sbcl-1.0.51 and tried the elephant test suite again;  I get
>> the same errors;  did the changes not make it into the newest sbcl release?
>
> They did.
>
> If someone can give me copy-pasteable-to-terminal/Slime instructions
> for running Elephants tests, I can take a second look. (It's
> non-obvious to me how to set up a store controller, and
> ASDF:TEST-SYSTEM doesn't do it for me, and FIVEAM:RUN<name-of-test>
> complains about it missing.)
>
> A snippet that reproduces the issue without depending on Elephant
> would be even better, but not required.
>
> Cheers,
>
>   -- nikodemus
>