From raison at chatsubo.net  Tue Apr 13 03:00:43 2010
From: raison at chatsubo.net (Kevin Raison)
Date: Mon, 12 Apr 2010 20:00:43 -0700
Subject: [elephant-devel] ClozureCL Status?
Message-ID: <4BC3DE5B.2060602@chatsubo.net>

I am curious what the official status of ClozureCL support is at this 
point?  I was very happy to find that using 64-bit FreeBSD 6.x, BDB 4.7 
and the CCL 1.5 release candidate, I see this when running the test 
suite for a fresh darcs checkout of Elephant 1.0:

  Did 508 checks.
     Pass: 508 (100%)
     Skip: 0 ( 0%)
     Fail: 0 ( 0%)

But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in 
strange ways, and never quite in the same way, but sometimes passes all 
tests.  Can anyone comment on the current plans for Clozure support? Are 
these known issues?

Some failure examples:

 > Error: Fault during read of memory address #xC2DC8
 > While executing: CCL::WRITE-ABBREVIATE-QUOTE, in process listener(1).

  or

Failure Details:
--------------------------------
FIXNUM-RANDOM-TEST []:
      Unexpected Error: #<CCL::CANT-CONSTRUCT-ARGLIST #x18AEFF86>
Can't construct argument list from (:TEST-EXPR 0 EQUAL VAR (DESERIALIZE 
(SERIALIZE VAR OUT-BUF *STORE-CONTROLLER*) *STORE-CONTROLLER*) 
#<TEST-CASE FIXNUM-RANDOM-TEST #x188C02B6> . "no reason given")...
--------------------------------

  or

 > Error: Fault during read of memory address #x99BE8
 > While executing: CCL::VALID-HEADER-P, in process listener(1).

  or

 > Error: Fault during read of memory address #x70BAC744
 > While executing: CCL::EQ-HASH-FIND, in process listener(1).

  or

 > Error: Fault during read of memory address #x8C1ED
 > While executing: CCL::%RETURN-ADDRESS-OFFSET, in process listener(1).

  or

Did 501 checks.
     Pass: 478 (95%)
     Skip: 0 ( 0%)
     Fail: 23 ( 4%)

  Failure Details:
  --------------------------------
  LARGER-INDEXING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 2)) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 8)) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 0)) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING []:
       (FIRST INSTANCES) evaluated to #<IDX-ONE-C oid:3580>, which is 
not EQUAL to NIL..
  --------------------------------
  --------------------------------
  LARGER-INDEXING []:
       (ELT INSTANCES 10) evaluated to #<IDX-ONE-C oid:3590>, which is 
not EQUAL to NIL..
  --------------------------------
  --------------------------------
  LARGER-INDEXING-WITH-STRING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "2")) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING-WITH-STRING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "8")) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING-WITH-STRING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "0")) evaluated 
to 20, which is not = to 10..
  --------------------------------
  --------------------------------
  LARGER-INDEXING-WITH-STRING []:
       (FIRST INSTANCES) evaluated to #<IDX-ONE-D oid:3480>, which is 
not EQUAL to NIL..
  --------------------------------
  --------------------------------
  LARGER-INDEXING-WITH-STRING []:
       (ELT INSTANCES 10) evaluated to #<IDX-ONE-D oid:3490>, which is 
not EQUAL to NIL..
  --------------------------------
  --------------------------------
  INDEXING-WITH-DUPSTUFF-BASIC []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
to 4, which is not = to 2..
  --------------------------------
  --------------------------------
  INDEXING-BASIC-WITH-SYMBOL []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'ONE)) 
evaluated to 4, which is not = to 2..
  --------------------------------
  --------------------------------
  INDEXING-BASIC-WITH-SYMBOL []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'TWO)) 
evaluated to 2, which is not = to 1..
  --------------------------------
  --------------------------------
  INDEXING-BASIC-WITH-SYMBOL []:
       (LIST INST2) evaluated to (#<IDX-ONE-E oid:2075>), which is not 
EQUAL to (NIL #<IDX-ONE-E oid:2075>)..
  --------------------------------
  --------------------------------
  INDEXING-BASIC []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
to 4, which is not = to 2..
  --------------------------------
  --------------------------------
  INDEXING-BASIC []:
       (LENGTH (GET-INSTANCES-BY-RANGE 'IDX-ONE-F 'SLOT1 N (+ 1 N))) 
evaluated to 5, which is not = to 3..
  --------------------------------
  --------------------------------
  INDEXING-MIXED []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
to 4, which is not = to 2..
  --------------------------------
  --------------------------------
  INDEXING-RANGE []:
       Unexpected Error: #<SIMPLE-ERROR #x1536FC0E>
There is no applicable method for the generic function:
   #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
when called with arguments:
   (NIL)..
  --------------------------------
  --------------------------------
  INDEXING-BASIC-WITH-STRING []:
       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-B 'SLOT1 "one")) 
evaluated to 4, which is not = to 2..
  --------------------------------
  --------------------------------
  INDEXING-BASIC-WITH-STRING []:
       (LIST INST2) evaluated to (#<IDX-ONE-B oid:2046>), which is not 
EQUAL to (NIL #<IDX-ONE-B oid:2046>)..
  --------------------------------
  --------------------------------
  INDEXING-RANGE-SIMPLE []:
       Unexpected Error: #<SIMPLE-ERROR #x153DCAFE>
There is no applicable method for the generic function:
   #<STANDARD-GENERIC-FUNCTION ELEPHANT::OID #x14BFC1CE>
when called with arguments:
   (NIL)..
  --------------------------------
  --------------------------------
  INDEXING-HIERARCHY []:
       Unexpected Error: #<SIMPLE-ERROR #x1530268E>
There is no applicable method for the generic function:
   #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
when called with arguments:
   (NIL)..
  --------------------------------
  --------------------------------
  INDEXING-CHANGE-CLASS []:
       1 evaluated to 1, which is not = to 2..
  --------------------------------




From eslick at media.mit.edu  Tue Apr 13 04:12:28 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Mon, 12 Apr 2010 21:12:28 -0700
Subject: [elephant-devel] ClozureCL Status?
In-Reply-To: <4BC3DE5B.2060602@chatsubo.net>
References: <4BC3DE5B.2060602@chatsubo.net>
Message-ID: <91B21A53-8A1A-4B18-90BF-EA4EAD351F3B@media.mit.edu>

I can't speak to the specific errors, although I'm just setting up my own x86-32bit Linux installation with ccl and Elephant so will let you know if I have problems.  

The errors in the tests look like you didn't clear out the test databases (there's a script in the test folder to do this).

Ian

On Apr 12, 2010, at 8:00 PM, Kevin Raison wrote:

> I am curious what the official status of ClozureCL support is at this 
> point?  I was very happy to find that using 64-bit FreeBSD 6.x, BDB 4.7 
> and the CCL 1.5 release candidate, I see this when running the test 
> suite for a fresh darcs checkout of Elephant 1.0:
> 
>  Did 508 checks.
>     Pass: 508 (100%)
>     Skip: 0 ( 0%)
>     Fail: 0 ( 0%)
> 
> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in 
> strange ways, and never quite in the same way, but sometimes passes all 
> tests.  Can anyone comment on the current plans for Clozure support? Are 
> these known issues?
> 
> Some failure examples:
> 
>> Error: Fault during read of memory address #xC2DC8
>> While executing: CCL::WRITE-ABBREVIATE-QUOTE, in process listener(1).
> 
>  or
> 
> Failure Details:
> --------------------------------
> FIXNUM-RANDOM-TEST []:
>      Unexpected Error: #<CCL::CANT-CONSTRUCT-ARGLIST #x18AEFF86>
> Can't construct argument list from (:TEST-EXPR 0 EQUAL VAR (DESERIALIZE 
> (SERIALIZE VAR OUT-BUF *STORE-CONTROLLER*) *STORE-CONTROLLER*) 
> #<TEST-CASE FIXNUM-RANDOM-TEST #x188C02B6> . "no reason given")...
> --------------------------------
> 
>  or
> 
>> Error: Fault during read of memory address #x99BE8
>> While executing: CCL::VALID-HEADER-P, in process listener(1).
> 
>  or
> 
>> Error: Fault during read of memory address #x70BAC744
>> While executing: CCL::EQ-HASH-FIND, in process listener(1).
> 
>  or
> 
>> Error: Fault during read of memory address #x8C1ED
>> While executing: CCL::%RETURN-ADDRESS-OFFSET, in process listener(1).
> 
>  or
> 
> Did 501 checks.
>     Pass: 478 (95%)
>     Skip: 0 ( 0%)
>     Fail: 23 ( 4%)
> 
>  Failure Details:
>  --------------------------------
>  LARGER-INDEXING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 2)) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 8)) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 0)) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING []:
>       (FIRST INSTANCES) evaluated to #<IDX-ONE-C oid:3580>, which is 
> not EQUAL to NIL..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING []:
>       (ELT INSTANCES 10) evaluated to #<IDX-ONE-C oid:3590>, which is 
> not EQUAL to NIL..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING-WITH-STRING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "2")) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING-WITH-STRING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "8")) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING-WITH-STRING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "0")) evaluated 
> to 20, which is not = to 10..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING-WITH-STRING []:
>       (FIRST INSTANCES) evaluated to #<IDX-ONE-D oid:3480>, which is 
> not EQUAL to NIL..
>  --------------------------------
>  --------------------------------
>  LARGER-INDEXING-WITH-STRING []:
>       (ELT INSTANCES 10) evaluated to #<IDX-ONE-D oid:3490>, which is 
> not EQUAL to NIL..
>  --------------------------------
>  --------------------------------
>  INDEXING-WITH-DUPSTUFF-BASIC []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
> to 4, which is not = to 2..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC-WITH-SYMBOL []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'ONE)) 
> evaluated to 4, which is not = to 2..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC-WITH-SYMBOL []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'TWO)) 
> evaluated to 2, which is not = to 1..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC-WITH-SYMBOL []:
>       (LIST INST2) evaluated to (#<IDX-ONE-E oid:2075>), which is not 
> EQUAL to (NIL #<IDX-ONE-E oid:2075>)..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
> to 4, which is not = to 2..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC []:
>       (LENGTH (GET-INSTANCES-BY-RANGE 'IDX-ONE-F 'SLOT1 N (+ 1 N))) 
> evaluated to 5, which is not = to 3..
>  --------------------------------
>  --------------------------------
>  INDEXING-MIXED []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated 
> to 4, which is not = to 2..
>  --------------------------------
>  --------------------------------
>  INDEXING-RANGE []:
>       Unexpected Error: #<SIMPLE-ERROR #x1536FC0E>
> There is no applicable method for the generic function:
>   #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
> when called with arguments:
>   (NIL)..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC-WITH-STRING []:
>       (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-B 'SLOT1 "one")) 
> evaluated to 4, which is not = to 2..
>  --------------------------------
>  --------------------------------
>  INDEXING-BASIC-WITH-STRING []:
>       (LIST INST2) evaluated to (#<IDX-ONE-B oid:2046>), which is not 
> EQUAL to (NIL #<IDX-ONE-B oid:2046>)..
>  --------------------------------
>  --------------------------------
>  INDEXING-RANGE-SIMPLE []:
>       Unexpected Error: #<SIMPLE-ERROR #x153DCAFE>
> There is no applicable method for the generic function:
>   #<STANDARD-GENERIC-FUNCTION ELEPHANT::OID #x14BFC1CE>
> when called with arguments:
>   (NIL)..
>  --------------------------------
>  --------------------------------
>  INDEXING-HIERARCHY []:
>       Unexpected Error: #<SIMPLE-ERROR #x1530268E>
> There is no applicable method for the generic function:
>   #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
> when called with arguments:
>   (NIL)..
>  --------------------------------
>  --------------------------------
>  INDEXING-CHANGE-CLASS []:
>       1 evaluated to 1, which is not = to 2..
>  --------------------------------
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From raison at chatsubo.net  Tue Apr 13 05:52:06 2010
From: raison at chatsubo.net (Kevin Raison)
Date: Mon, 12 Apr 2010 22:52:06 -0700
Subject: [elephant-devel] ClozureCL Status?
In-Reply-To: <91B21A53-8A1A-4B18-90BF-EA4EAD351F3B@media.mit.edu>
References: <4BC3DE5B.2060602@chatsubo.net>
	<91B21A53-8A1A-4B18-90BF-EA4EAD351F3B@media.mit.edu>
Message-ID: <4BC40686.3040905@chatsubo.net>

Ian, I tried again, making absolutely sure to clean out the test 
directories using delscript.sh.  In this case, I always see some sort of 
memory fault, such as

 > Error: Fault during read of memory address #x1939A388
 > While executing: CCL::%BIGNUM-SIGN, in process listener(1).

And the tests never run to completion.

-Kevin


On 04/12/2010 09:12 PM, Ian Eslick wrote:
> I can't speak to the specific errors, although I'm just setting up my own x86-32bit Linux installation with ccl and Elephant so will let you know if I have problems.
>
> The errors in the tests look like you didn't clear out the test databases (there's a script in the test folder to do this).
>
> Ian
>
> On Apr 12, 2010, at 8:00 PM, Kevin Raison wrote:
>
>> I am curious what the official status of ClozureCL support is at this
>> point?  I was very happy to find that using 64-bit FreeBSD 6.x, BDB 4.7
>> and the CCL 1.5 release candidate, I see this when running the test
>> suite for a fresh darcs checkout of Elephant 1.0:
>>
>>   Did 508 checks.
>>      Pass: 508 (100%)
>>      Skip: 0 ( 0%)
>>      Fail: 0 ( 0%)
>>
>> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in
>> strange ways, and never quite in the same way, but sometimes passes all
>> tests.  Can anyone comment on the current plans for Clozure support? Are
>> these known issues?
>>
>> Some failure examples:
>>
>>> Error: Fault during read of memory address #xC2DC8
>>> While executing: CCL::WRITE-ABBREVIATE-QUOTE, in process listener(1).
>>
>>   or
>>is not of the expected type MACPTR.
>> Failure Details:
>> --------------------------------
>> FIXNUM-RANDOM-TEST []:
>>       Unexpected Error: #<CCL::CANT-CONSTRUCT-ARGLIST #x18AEFF86>
>> Can't construct argument list from (:TEST-EXPR 0 EQUAL VAR (DESERIALIZE
>> (SERIALIZE VAR OUT-BUF *STORE-CONTROLLER*) *STORE-CONTROLLER*)
>> #<TEST-CASE FIXNUM-RANDOM-TEST #x188C02B6>  . "no reason given")...
>> --------------------------------
>>
>>   or
>>
>>> Error: Fault during read of memory address #x99BE8
>>> While executing: CCL::VALID-HEADER-P, in process listener(1).
>>
>>   or
>>
>>> Error: Fault during read of memory address #x70BAC744
>>> While executing: CCL::EQ-HASH-FIND, in process listener(1).
>>
>>   or
>>
>>> Error: Fault during read of memory address #x8C1ED
>>> While executing: CCL::%RETURN-ADDRESS-OFFSET, in process listener(1).
>>
>>   or
>>
>> Did 501 checks.
>>      Pass: 478 (95%)
>>      Skip: 0 ( 0%)
>>      Fail: 23 ( 4%)
>>
>>   Failure Details:
>>   --------------------------------
>>   LARGER-INDEXING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 2)) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 8)) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 0)) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING []:
>>        (FIRST INSTANCES) evaluated to #<IDX-ONE-C oid:3580>, which is
>> not EQUAL to NIL..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING []:
>>        (ELT INSTANCES 10) evaluated to #<IDX-ONE-C oid:3590>, which is
>> not EQUAL to NIL..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING-WITH-STRING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "2")) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING-WITH-STRING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "8")) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING-WITH-STRING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "0")) evaluated
>> to 20, which is not = to 10..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING-WITH-STRING []:
>>        (FIRST INSTANCES) evaluated to #<IDX-ONE-D oid:3480>, which is
>> not EQUAL to NIL..
>>   --------------------------------
>>   --------------------------------
>>   LARGER-INDEXING-WITH-STRING []:
>>        (ELT INSTANCES 10) evaluated to #<IDX-ONE-D oid:3490>, which is
>> not EQUAL to NIL..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-WITH-DUPSTUFF-BASIC []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>> to 4, which is not = to 2..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC-WITH-SYMBOL []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'ONE))
>> evaluated to 4, which is not = to 2..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC-WITH-SYMBOL []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'TWO))
>> evaluated to 2, which is not = to 1..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC-WITH-SYMBOL []:
>>        (LIST INST2) evaluated to (#<IDX-ONE-E oid:2075>), which is not
>> EQUAL to (NIL #<IDX-ONE-E oid:2075>)..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>> to 4, which is not = to 2..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC []:
>>        (LENGTH (GET-INSTANCES-BY-RANGE 'IDX-ONE-F 'SLOT1 N (+ 1 N)))
>> evaluated to 5, which is not = to 3..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-MIXED []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>> to 4, which is not = to 2..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-RANGE []:
>>        Unexpected Error: #<SIMPLE-ERROR #x1536FC0E>
>> There is no applicable method for the generic function:
>>    #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
>> when called with arguments:
>>    (NIL)..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC-WITH-STRING []:
>>        (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-B 'SLOT1 "one"))
>> evaluated to 4, which is not = to 2..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-BASIC-WITH-STRING []:
>>        (LIST INST2) evaluated to (#<IDX-ONE-B oid:2046>), which is not
>> EQUAL to (NIL #<IDX-ONE-B oid:2046>)..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-RANGE-SIMPLE []:
>>        Unexpected Error: #<SIMPLE-ERROR #x153DCAFE>
>> There is no applicable method for the generic function:
>>    #<STANDARD-GENERIC-FUNCTION ELEPHANT::OID #x14BFC1CE>
>> when called with arguments:
>>    (NIL)..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-HIERARCHY []:
>>        Unexpected Error: #<SIMPLE-ERROR #x1530268E>
>> There is no applicable method for the generic function:
>>    #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
>> when called with arguments:
>>    (NIL)..
>>   --------------------------------
>>   --------------------------------
>>   INDEXING-CHANGE-CLASS []:
>>        1 evaluated to 1, which is not = to 2..
>>   --------------------------------
>>
>>
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/elephant-devel
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel



From sky at viridian-project.de  Tue Apr 13 06:57:53 2010
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Tue, 13 Apr 2010 08:57:53 +0200 (CEST)
Subject: [elephant-devel] ClozureCL Status?
In-Reply-To: <4BC3DE5B.2060602@chatsubo.net>
References: <4BC3DE5B.2060602@chatsubo.net>
Message-ID: <e8fabe115096cbd8e42bcd50db7074c5.squirrel@mail.stardawn.org>


Hey Kevin,

you wrote:

> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in
> strange ways, and never quite in the same way, but sometimes passes all
> tests.  Can anyone comment on the current plans for Clozure support? Are
> these known issues?

The last version of CCL that I worked with was 1.3, and I didn't see
errors of this kind.

I suspect a problem in CCL; try asking on openmcl-devel.

  Leslie




From eslick at media.mit.edu  Tue Apr 13 18:46:54 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Tue, 13 Apr 2010 11:46:54 -0700
Subject: [elephant-devel] ClozureCL Status?
In-Reply-To: <e8fabe115096cbd8e42bcd50db7074c5.squirrel@mail.stardawn.org>
References: <4BC3DE5B.2060602@chatsubo.net>
	<e8fabe115096cbd8e42bcd50db7074c5.squirrel@mail.stardawn.org>
Message-ID: <8161101E-E4D3-4F78-B3C1-CC8BB17D1BF8@media.mit.edu>

I'm using the development head of CCL on a 32-bit linux and am running into the same memory fault.  I'll reach out to the devs.

Ian

On Apr 12, 2010, at 11:57 PM, Leslie P. Polzer wrote:

> 
> Hey Kevin,
> 
> you wrote:
> 
>> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in
>> strange ways, and never quite in the same way, but sometimes passes all
>> tests.  Can anyone comment on the current plans for Clozure support? Are
>> these known issues?
> 
> The last version of CCL that I worked with was 1.3, and I didn't see
> errors of this kind.
> 
> I suspect a problem in CCL; try asking on openmcl-devel.
> 
> Leslie
> 
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From eslick at media.mit.edu  Tue Apr 13 18:47:01 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Tue, 13 Apr 2010 11:47:01 -0700
Subject: [elephant-devel] ClozureCL Status?
In-Reply-To: <4BC40686.3040905@chatsubo.net>
References: <4BC3DE5B.2060602@chatsubo.net>
	<91B21A53-8A1A-4B18-90BF-EA4EAD351F3B@media.mit.edu>
	<4BC40686.3040905@chatsubo.net>
Message-ID: <27341619-4D45-42C8-B2DA-B31A5A9EB82F@media.mit.edu>

Can you try with an earlier version?  Say CCL 1.3?

This may be due to changes in the 32-bit compiler which has a very different compiler backend than the 64-bit which I've been using fine on linux Intel and AMD x86 machines.

On Apr 12, 2010, at 10:52 PM, Kevin Raison wrote:

> Ian, I tried again, making absolutely sure to clean out the test 
> directories using delscript.sh.  In this case, I always see some sort of 
> memory fault, such as
> 
>> Error: Fault during read of memory address #x1939A388
>> While executing: CCL::%BIGNUM-SIGN, in process listener(1).
> 
> And the tests never run to completion.
> 
> -Kevin
> 
> 
> On 04/12/2010 09:12 PM, Ian Eslick wrote:
>> I can't speak to the specific errors, although I'm just setting up my own x86-32bit Linux installation with ccl and Elephant so will let you know if I have problems.
>> 
>> The errors in the tests look like you didn't clear out the test databases (there's a script in the test folder to do this).
>> 
>> Ian
>> 
>> On Apr 12, 2010, at 8:00 PM, Kevin Raison wrote:
>> 
>>> I am curious what the official status of ClozureCL support is at this
>>> point?  I was very happy to find that using 64-bit FreeBSD 6.x, BDB 4.7
>>> and the CCL 1.5 release candidate, I see this when running the test
>>> suite for a fresh darcs checkout of Elephant 1.0:
>>> 
>>> Did 508 checks.
>>>    Pass: 508 (100%)
>>>    Skip: 0 ( 0%)
>>>    Fail: 0 ( 0%)
>>> 
>>> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in
>>> strange ways, and never quite in the same way, but sometimes passes all
>>> tests.  Can anyone comment on the current plans for Clozure support? Are
>>> these known issues?
>>> 
>>> Some failure examples:
>>> 
>>>> Error: Fault during read of memory address #xC2DC8
>>>> While executing: CCL::WRITE-ABBREVIATE-QUOTE, in process listener(1).
>>> 
>>> or
>>> is not of the expected type MACPTR.
>>> Failure Details:
>>> --------------------------------
>>> FIXNUM-RANDOM-TEST []:
>>>     Unexpected Error: #<CCL::CANT-CONSTRUCT-ARGLIST #x18AEFF86>
>>> Can't construct argument list from (:TEST-EXPR 0 EQUAL VAR (DESERIALIZE
>>> (SERIALIZE VAR OUT-BUF *STORE-CONTROLLER*) *STORE-CONTROLLER*)
>>> #<TEST-CASE FIXNUM-RANDOM-TEST #x188C02B6>  . "no reason given")...
>>> --------------------------------
>>> 
>>> or
>>> 
>>>> Error: Fault during read of memory address #x99BE8
>>>> While executing: CCL::VALID-HEADER-P, in process listener(1).
>>> 
>>> or
>>> 
>>>> Error: Fault during read of memory address #x70BAC744
>>>> While executing: CCL::EQ-HASH-FIND, in process listener(1).
>>> 
>>> or
>>> 
>>>> Error: Fault during read of memory address #x8C1ED
>>>> While executing: CCL::%RETURN-ADDRESS-OFFSET, in process listener(1).
>>> 
>>> or
>>> 
>>> Did 501 checks.
>>>    Pass: 478 (95%)
>>>    Skip: 0 ( 0%)
>>>    Fail: 23 ( 4%)
>>> 
>>> Failure Details:
>>> --------------------------------
>>> LARGER-INDEXING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 2)) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 8)) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-C 'SLOT1 0)) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING []:
>>>      (FIRST INSTANCES) evaluated to #<IDX-ONE-C oid:3580>, which is
>>> not EQUAL to NIL..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING []:
>>>      (ELT INSTANCES 10) evaluated to #<IDX-ONE-C oid:3590>, which is
>>> not EQUAL to NIL..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING-WITH-STRING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "2")) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING-WITH-STRING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "8")) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING-WITH-STRING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-D 'SLOT1 "0")) evaluated
>>> to 20, which is not = to 10..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING-WITH-STRING []:
>>>      (FIRST INSTANCES) evaluated to #<IDX-ONE-D oid:3480>, which is
>>> not EQUAL to NIL..
>>> --------------------------------
>>> --------------------------------
>>> LARGER-INDEXING-WITH-STRING []:
>>>      (ELT INSTANCES 10) evaluated to #<IDX-ONE-D oid:3490>, which is
>>> not EQUAL to NIL..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-WITH-DUPSTUFF-BASIC []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>>> to 4, which is not = to 2..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC-WITH-SYMBOL []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'ONE))
>>> evaluated to 4, which is not = to 2..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC-WITH-SYMBOL []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-E 'SLOT1 'TWO))
>>> evaluated to 2, which is not = to 1..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC-WITH-SYMBOL []:
>>>      (LIST INST2) evaluated to (#<IDX-ONE-E oid:2075>), which is not
>>> EQUAL to (NIL #<IDX-ONE-E oid:2075>)..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>>> to 4, which is not = to 2..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC []:
>>>      (LENGTH (GET-INSTANCES-BY-RANGE 'IDX-ONE-F 'SLOT1 N (+ 1 N)))
>>> evaluated to 5, which is not = to 3..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-MIXED []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-F 'SLOT1 N)) evaluated
>>> to 4, which is not = to 2..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-RANGE []:
>>>      Unexpected Error: #<SIMPLE-ERROR #x1536FC0E>
>>> There is no applicable method for the generic function:
>>>  #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
>>> when called with arguments:
>>>  (NIL)..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC-WITH-STRING []:
>>>      (LENGTH (GET-INSTANCES-BY-VALUE 'IDX-ONE-B 'SLOT1 "one"))
>>> evaluated to 4, which is not = to 2..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-BASIC-WITH-STRING []:
>>>      (LIST INST2) evaluated to (#<IDX-ONE-B oid:2046>), which is not
>>> EQUAL to (NIL #<IDX-ONE-B oid:2046>)..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-RANGE-SIMPLE []:
>>>      Unexpected Error: #<SIMPLE-ERROR #x153DCAFE>
>>> There is no applicable method for the generic function:
>>>  #<STANDARD-GENERIC-FUNCTION ELEPHANT::OID #x14BFC1CE>
>>> when called with arguments:
>>>  (NIL)..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-HIERARCHY []:
>>>      Unexpected Error: #<SIMPLE-ERROR #x1530268E>
>>> There is no applicable method for the generic function:
>>>  #<STANDARD-GENERIC-FUNCTION SLOT1 #x1512367E>
>>> when called with arguments:
>>>  (NIL)..
>>> --------------------------------
>>> --------------------------------
>>> INDEXING-CHANGE-CLASS []:
>>>      1 evaluated to 1, which is not = to 2..
>>> --------------------------------
>>> 
>>> 
>>> _______________________________________________
>>> elephant-devel site list
>>> elephant-devel at common-lisp.net
>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>> 
>> 
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/elephant-devel
> 
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel




From eslick at media.mit.edu  Tue Apr 13 19:48:19 2010
From: eslick at media.mit.edu (Ian Eslick)
Date: Tue, 13 Apr 2010 12:48:19 -0700
Subject: [elephant-devel] CCL 1.3
Message-ID: <86BDDEFA-3070-4610-9A7A-75627BBA89AB@media.mit.edu>

Ok, it is missing a function that elephant depends on.  I've sent a mail to the ccl developer list.

Ian


From rme at clozure.com  Mon Apr 19 17:24:24 2010
From: rme at clozure.com (R. Matthew Emerson)
Date: Mon, 19 Apr 2010 13:24:24 -0400
Subject: [elephant-devel] memutil.lisp using ccl's memory accessors
Message-ID: <4358C95A-FFEA-4A4D-B008-AF98407217CA@clozure.com>

Here's a patch that uses Clozure CL's built-in foreign memory accessors instead of calling out to foreign functions in libmemutil.

I tested it with a trunk ccl on Darwin/x8632.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ccl-libmemutil.patch
Type: application/octet-stream
Size: 18822 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20100419/f7419931/attachment.obj>

From ron at flownet.com  Tue Apr 20 22:30:18 2010
From: ron at flownet.com (Ron Garret)
Date: Tue, 20 Apr 2010 15:30:18 -0700
Subject: [elephant-devel] Why does an empty BDB repository take 40 MB?
Message-ID: <A6EA983C-F952-46FA-B35C-F1DB2A9360FC@flownet.com>

SLSIA.  I create a brand new BDB-backed elephant repository and it takes up 40MB of disk space.  Why?

Thanks,
rg




From sky at viridian-project.de  Wed Apr 21 08:51:46 2010
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Wed, 21 Apr 2010 10:51:46 +0200 (CEST)
Subject: [elephant-devel] Why does an empty BDB repository take 40 MB?
In-Reply-To: <A6EA983C-F952-46FA-B35C-F1DB2A9360FC@flownet.com>
References: <A6EA983C-F952-46FA-B35C-F1DB2A9360FC@flownet.com>
Message-ID: <f3474ca21610ecc79a16d4e27f78bc25.squirrel@mail.stardawn.org>


Ron Garret wrote:
> SLSIA.  I create a brand new BDB-backed elephant repository
> and it takes up 40MB of disk space.  Why?

Elephant creates some btrees as part of repository initialization.

What you're seeing is probably a combination of BDB log files (try to
invoke db_archive with the -d switch[1]) and preallocated disk space
(to avoid excessive fragmentation when the tree is filled).

That's an educated guess, I haven't looked at it.

  Leslie

[1]
http://www.oracle.com/technology/documentation/berkeley-db/db/api_reference/C/db_archive.html




From quasilists at gmail.com  Wed Apr 21 21:01:02 2010
From: quasilists at gmail.com (quasi)
Date: Thu, 22 Apr 2010 02:31:02 +0530
Subject: [elephant-devel] bdb licensing text from section 9.4
Message-ID: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com>

Hey guys,

Thanks for Elephant. I am just starting to use it.  I have a question
regarding the following :

Section "9.4 Data Store Licensing Considerations" from the manual
states the following

"... In most interpretations of the license, this includes a
requirement to make code available for the entirety of any publicly
visible website that is based on Berkeley DB."

This was rather disturbing (to me) so I read the license documentation
from the oracle site and it is quite ambiguous about above stated
point. A little bit more googleling and I found an interview with
Sleepycat President and CEO, Michael Olson from 2001 here :
http://www.winterspeak.com/columns/102901.html

I quote him "Building a Web service on top of Berkeley DB and making
it available via HTTP doesn't require payment or release of code."

Is Oracle is still using the Sleepycat licence or have they changed it
?  I was planning to build a website with a berkeley db backend using
Elephant. Is this not recommended due to licensing issues ? This would
be a commercial website and I would not want to release the code.

I am unclear and would appreciate any suggestions regarding this.

thanks,
Abhijit Rao (quasi)



From sky at viridian-project.de  Thu Apr 22 07:35:46 2010
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Thu, 22 Apr 2010 09:35:46 +0200 (CEST)
Subject: [elephant-devel] bdb licensing text from section 9.4
In-Reply-To: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com>
References: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com>
Message-ID: <07f9f13b70d488a883305bb9fcf4a3df.squirrel@mail.stardawn.org>


quasi wrote:

> Is Oracle is still using the Sleepycat licence or have they changed it
> ?  I was planning to build a website with a berkeley db backend using
> Elephant. Is this not recommended due to licensing issues ? This would
> be a commercial website and I would not want to release the code.

I'm not a lawyer, but here are some hints:

  * the license is controversial in this regard but the general consensus
    seems to be that Oracle doesn't charge licensing fees from web sites
    using BDB.

  * they seem to have changed their licensing FAQ, but I remember the
    old one saying that your app is not affected by BDB's license if
    it is using a library that in turn uses BDB.

  * to get more reliable information, write to berkeleydb-info_us at oracle.com

Hope that helps...

 Leslie




From killerstorm at newmail.ru  Thu Apr 22 10:20:01 2010
From: killerstorm at newmail.ru (Alex Mizrahi)
Date: Thu, 22 Apr 2010 13:20:01 +0300
Subject: [elephant-devel] Why does an empty BDB repository take 40 MB?
References: <A6EA983C-F952-46FA-B35C-F1DB2A9360FC@flownet.com>
	<f3474ca21610ecc79a16d4e27f78bc25.squirrel@mail.stardawn.org>
Message-ID: <hqp7sq$ko8$1@dough.gmane.org>

 ??>> SLSIA.  I create a brand new BDB-backed elephant repository
 ??>> and it takes up 40MB of disk space.  Why?

 LPP> Elephant creates some btrees as part of repository initialization.

 LPP> What you're seeing is probably a combination of BDB log files (try to
 LPP> invoke db_archive with the -d switch[1]) and preallocated disk space
 LPP> (to avoid excessive fragmentation when the tree is filled).

You're right, but files it pre-allocates are sparse, which means it's much 
less of a problem w.r.t. disk space.
Here're results of my investigation (as seen in comp.lang.lisp):

----
BerkeleyDB creates large files for its work:

alex at debetch:~/foobla$ ls -l
-rw-r----- 1 alex alex    24576 2010-04-21 01:37 __db.001
-rw-r----- 1 alex alex  1327104 2010-04-21 01:37 __db.002
-rw-r----- 1 alex alex 26222592 2010-04-21 01:37 __db.003
-rw-r----- 1 alex alex    98304 2010-04-21 01:37 __db.004
-rw-r----- 1 alex alex   557056 2010-04-21 01:37 __db.005
-rw-r----- 1 alex alex   253952 2010-04-21 01:37 __db.006
-rw-r----- 1 alex alex    40960 2010-04-21 01:33 %ELEPHANT
-rw-r----- 1 alex alex    16384 2010-04-21 01:32 %ELEPHANTDUP
-rw-r----- 1 alex alex    16384 2010-04-21 01:33 %ELEPHANTOID
-rw-r----- 1 alex alex 10485760 2010-04-21 01:33 log.0000000001

But those files are sparse, they do not eat space on disk until they are
populated:

alex at debetch:~/foobla$ du -h
2.0M    .

alex at debetch:~/foobla$ du -h *
12K     __db.001
1.1M    __db.002
296K    __db.003
24K     __db.004
364K    __db.005
16K     __db.006
40K     %ELEPHANT
16K     %ELEPHANTDUP
16K     %ELEPHANTOID
104K    log.0000000001

alex at debetch:~$ tar czf foobla.tgz foobla
alex at debetch:~$ ls -l foobla.tgz
-rw-r--r-- 1 alex alex 86029 2010-04-21 01:40 foobla.tgz

Well, if you use filesystem which supports sparse files.
If you don't like this anyway, you can configure BDB to allocate smaller
files.
File __db.003 seems to be related to cache size, default cache in
config.sexp is 20MB.
If you set it to 256KiB (default for BDB) in my-config.sexp:

 (:BERKELEY-DB-CACHESIZE . 262144)

You won't have that large file:
-rw-r----- 1 alex alex    24576 2010-04-21 01:54 __db.001
-rw-r----- 1 alex alex   385024 2010-04-21 01:54 __db.002
-rw-r----- 1 alex alex   335872 2010-04-21 01:54 __db.003
-rw-r----- 1 alex alex    98304 2010-04-21 01:54 __db.004
-rw-r----- 1 alex alex   557056 2010-04-21 01:54 __db.005
-rw-r----- 1 alex alex   253952 2010-04-21 01:54 __db.006
-rw-r----- 1 alex alex    40960 2010-04-21 01:54 %ELEPHANT
-rw-r----- 1 alex alex    16384 2010-04-21 01:54 %ELEPHANTDUP
-rw-r----- 1 alex alex    16384 2010-04-21 01:54 %ELEPHANTOID
-rw-r----- 1 alex alex 10485760 2010-04-21 01:54 log.0000000001

There is also 10 MiB log file. It is default size for BDB. There is no good
way to tweak in Elephant, but there is BDB API for this, so it's possible to
implement it, if you think it is really needed.
---- 





From killerstorm at newmail.ru  Thu Apr 22 10:58:59 2010
From: killerstorm at newmail.ru (Alex Mizrahi)
Date: Thu, 22 Apr 2010 13:58:59 +0300
Subject: [elephant-devel] bdb licensing text from section 9.4
References: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com>
Message-ID: <hqpa5r$sv6$1@dough.gmane.org>

 q> This was rather disturbing (to me) so I read the license documentation
 q> from the oracle site and it is quite ambiguous about above stated
 q> point.

I don't think it is ambigous. License only restricts _redistribution_ (if 
you redistribute, you must also release source code), but it doesn't 
restrict use itself.
What exactly redistribution means is further explained in licensing Q&A:

http://www.oracle.com/technology/software/products/berkeley-db/htdocs/licensing.html
-----
What does "redistribute" mean?

The term "redistribution" in the Open Source License means your application 
is distributed to one or more third parties. Giving an application to 
customers, even in alpha or beta releases, is redistribution. Giving 
contractors, affiliates, parent organizations or subsidiaries, business 
partners or support vendors a copy of the application is generally 
redistribution.

The following are not redistribution:
Building an application for use internal to your organization, deployed and 
managed on your company servers.
Off-site backups or other software archival procedures.

If you have questions about whether your use of Berkeley DB, Berkeley DB 
Java Edition or Berkeley DB XML constitutes redistribution, please contact 
us at berkeleydb-info_us at oracle.com.
-----

I think it is pretty clear -- if you do not give your application that is 
using BDB in source or binary form to third parties, you're ok.
That is, using it for web site should be ok.

But nobody can _guarantee_  that you're safe. :)

If we compare it to other licenses, I believe license Oracle uses for BDB is 
very similar to GPL, with GPL being more verbose and more restrictive.

And so we can compare BDB to GPL-licensed MySQL (and, by the way, MySQL is 
currently also owned by Oracle).
MySQL's interpretation of licensing issues were intentionally vague (like, 
"if you're a commercial company, why don't you just buy it and forget about 
this legalese mumbo-jumbo"), but de-facto a lot of web sites just use MySQL 
without any problems.

In general, there is consensus that GPL does not forbid using GPL'd 
libraries in closed-source applications which work on company's servers 
(like web sites) -- it is known as "application service provider loophole", 
and for this reason a different license which covers network use was 
created -- it is called AGPL. 





From quasilists at gmail.com  Thu Apr 22 15:06:09 2010
From: quasilists at gmail.com (quasi)
Date: Thu, 22 Apr 2010 20:36:09 +0530
Subject: [elephant-devel] bdb licensing text from section 9.4
In-Reply-To: <hqpa5r$sv6$1@dough.gmane.org>
References: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com>
	<hqpa5r$sv6$1@dough.gmane.org>
Message-ID: <x2y438e11131004220806v1254a709x843f11039d0d541c@mail.gmail.com>

On Thu, Apr 22, 2010 at 4:28 PM, Alex Mizrahi <killerstorm at newmail.ru> wrote:
[snip]
>
> I think it is pretty clear -- if you do not give your application that is
> using BDB in source or binary form to third parties, you're ok.
> That is, using it for web site should be ok.

This was precisely my understanding, but the text in the elephant
documentation threw me off. Would it be better to change that as it
leads to some confusion?

Thanks guys,

Abhijit



From killerstorm at newmail.ru  Thu Apr 22 15:43:58 2010
From: killerstorm at newmail.ru (Alex Mizrahi)
Date: Thu, 22 Apr 2010 18:43:58 +0300
Subject: [elephant-devel] bdb licensing text from section 9.4
References: <z2h438e11131004211401pa8119fa5vb9e0196454fdfcd4@mail.gmail.com><hqpa5r$sv6$1@dough.gmane.org>
	<x2y438e11131004220806v1254a709x843f11039d0d541c@mail.gmail.com>
Message-ID: <hqpqs8$4d6$1@dough.gmane.org>

 ??>> I think it is pretty clear -- if you do not give your application that
 ??>> is using BDB in source or binary form to third parties, you're
 ??>> ok. That is, using it for web site should be ok.

 q> This was precisely my understanding, but the text in the elephant
 q> documentation threw me off. Would it be better to change that as it
 q> leads to some confusion?

Sure.
It also incorrectly calls BDB "GPL'd software", while it is covered by 
Sleepycat license. This is just plainly wrong.
So it needs to be fixed.





From quasilists at gmail.com  Fri Apr 23 20:30:55 2010
From: quasilists at gmail.com (quasi)
Date: Sat, 24 Apr 2010 02:00:55 +0530
Subject: [elephant-devel] persistant class compilation error
Message-ID: <q2r438e11131004231330l4c5814b2w31d04ed46caa23d7@mail.gmail.com>

Hey guys,

I am using elephant 1.0 (stable) pulled from darcs. When I try to
compile a persistant class (in slime) I get the following attached
error. When I compile it
the second time it compiles fine.

I am using SBCL 1.0.32 on OSX with :x86-64 & :sb-thread.

thanks!
Abhijit

(defclass foo2 ()
  ((foo :accessor foo :initarg :foo :documentation "foo")
   (bar :accessor bar :initarg :bar :documentation "bar"))
  (:metaclass ele:persistent-metaclass))


There is no class named FOO2.
   [Condition of type SIMPLE-ERROR]

Restarts:
 0: [ABORT] Abort compilation.
 1: [ABORT] Return to SLIME's top level.
 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker"
RUNNING {1002C626D1}>)

Backtrace:
  0: (SB-PCL::REAL-ADD-METHOD #<STANDARD-GENERIC-FUNCTION FOO (1)>
#<SB-MOP:STANDARD-READER-METHOD FOO, slot:FOO, ((CLASS #))
{1002C85811}> NIL)
      Locals:
        GENERIC-FUNCTION = #<STANDARD-GENERIC-FUNCTION FOO (1)>
        METHOD = #<SB-MOP:STANDARD-READER-METHOD FOO, slot:FOO,
((CLASS ..)) {1002C85811}>
        SB-PCL::SKIP-DFUN-UPDATE-P = NIL
  1: (SB-PCL::FIX-SLOT-ACCESSORS ..)
      Locals:
        SB-PCL::ADD/REMOVE = SB-PCL::ADD
        CLASS = #<ELEPHANT:PERSISTENT-METACLASS FOO2>
        SB-PCL::DSLOTDS =
(#<ELEPHANT::PERSISTENT-DIRECT-SLOT-DEFINITION FOO> ..)
        SB-PCL::SOURCE-LOCATION = #S(SB-C:DEFINITION-SOURCE-LOCATION ..)
  2: ((SB-PCL::FAST-METHOD SHARED-INITIALIZE :AFTER (SB-PCL::STD-CLASS
T)) #(17 NIL 5 NIL) #<unavailable argument>
#<ELEPHANT:PERSISTENT-METACLASS FOO2> T)[:EXTERNAL]
      Locals:
        SB-DEBUG::ARG-0 = 16
        SB-DEBUG::ARG-1 = #(17 NIL 5 NIL)
        SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-3 = #<ELEPHANT:PERSISTENT-METACLASS FOO2>
        SB-DEBUG::ARG-4 = T
  3: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0.
SB-PCL::.ARG1. SB-INT:&MORE SB-PCL::.DFUN-MORE-CONTEXT.
SB-PCL::.DFUN-MORE-COUNT.)) ..)
      Locals:
        SB-PCL::.ARG0. = #<ELEPHANT:PERSISTENT-METACLASS FOO2>
        SB-PCL::.ARG1. = T
        SB-PCL::.DFUN-MORE-CONTEXT. = 16023515
        SB-PCL::.DFUN-MORE-COUNT. = 12
  4: ((SB-PCL::FAST-METHOD SHARED-INITIALIZE :AROUND
(ELEPHANT:PERSISTENT-METACLASS T)) #<unavailable argument>
#<unavailable argument> #<unavailable argument> #<unavailable
argument>)[:EXTERNAL]
      Locals:
        SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-3 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-4 = :<NOT-AVAILABLE>
  5: ((SB-PCL::FAST-METHOD MAKE-INSTANCE (CLASS)) #<unavailable
argument> #<unavailable argument> #<STANDARD-CLASS
ELEPHANT:PERSISTENT-METACLASS>)[:EXTERNAL]
      Locals:
        SB-DEBUG::ARG-0 = 15
        SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
        SB-DEBUG::ARG-3 = #<STANDARD-CLASS ELEPHANT:PERSISTENT-METACLASS>
  6: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
      [No Locals]
  7: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291))
  8: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..)
  9: ((SB-PCL::FAST-METHOD SB-MOP:ENSURE-CLASS-USING-CLASS (NULL T))
#<unavailable argument> #<unavailable argument> NIL FOO2)[:EXTERNAL]
 10: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291))
 11: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..)
 12: (SB-MOP:ENSURE-CLASS FOO2)[:EXTERNAL]
 13: (SB-PCL::REAL-LOAD-DEFCLASS ..)
 14: (SB-FASL::LOAD-FASL-GROUP #<SB-SYS:FD-STREAM for "file
/private/var/tmp/tmp.fasl" {1002C7CE51}>)
 15: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK))
 16: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]291))
 17: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK ..)
 18: (SB-FASL::LOAD-AS-FASL #<SB-SYS:FD-STREAM for "file
/private/var/tmp/tmp.fasl" {1002C7CE51}> NIL #<unavailable argument>)
 19: ((FLET SB-FASL::LOAD-STREAM) #<SB-SYS:FD-STREAM for "file
/private/var/tmp/tmp.fasl" {1002C7CE51}> T)
 --more--


-- 
Abhijit Rao (quasi)

REd Pill is Lisp.



From sky at viridian-project.de  Sat Apr 24 08:07:53 2010
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Sat, 24 Apr 2010 10:07:53 +0200 (CEST)
Subject: [elephant-devel] persistant class compilation error
In-Reply-To: <q2r438e11131004231330l4c5814b2w31d04ed46caa23d7@mail.gmail.com>
References: <q2r438e11131004231330l4c5814b2w31d04ed46caa23d7@mail.gmail.com>
Message-ID: <8ece0ca46def46049972f60278730a12.squirrel@mail.stardawn.org>


Hello Abhijit,

I remember having fixed this bug some months ago. Please try the
latest head of Elephant 1.0 via

  darcs get http://www.common-lisp.net/project/elephant/darcs/elephant-1.0

 Leslie