2008 at 10:18 AM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> Just to ask the basic questions. Which BDB are you using and does your
> my-config.sexp match that version?
>
> Ian
>
> On Jun 1, 2008, at 11:44 PM, Leonardo Varuzza wrote:
>
>> Hello,
>>
>> If I chan
Hello,
If I change the declaim in the top of berkeley-db.lisp to (safety 3)
(debug 3), I got this error from SBCL 1.0.17 on AMD64:
invalid number of arguments: 1
[Condition of type SB-INT:SIMPLE-PROGRAM-ERROR]
Restarts:
0: [ABORT-REQUEST] Abort handling SLIME request.
1: [TERMINATE-THREAD
Ops, it's 1.0.16.11 the latest version from CVS. Today I tested with
1.0.16 and the error is gone.
You are right about a bug in the SBCL.
On Sun, Apr 27, 2008 at 1:59 PM, Alex Mizrahi <[EMAIL PROTECTED]> wrote:
> LV> I have this bug when compiling elephant on SBCL 1.16.11 (latest
> LV> versio
I have this bug when compiling elephant on SBCL 1.16.11 (latest
version) runing on Ubuntu 8.04 x86-64:
no :MOVE-ARG VOP defined to move # (SC SB-VM::SINGLE-REG)
to # (SC SB-VM::ANY-REG)
[Condition of type SIMPLE-ERROR]
Restarts:
0: [RETRY] Retry performing # on
#.
1: [ACCEPT] Continue, tre
src/memutil/libmemutil.so
> -lm "))
> 14: (ASDF:RUN-SHELL-COMMAND "~A ~{~A ~}")
> 15: ((SB-PCL::FAST-METHOD ASDF:PERFORM
>(ASDF:COMPILE-OP ELEPHANT-SYSTEM:ELEPHANT-C-SOURCE))
> #
> #
> #
> #)
> 16: ((LAMBDA
>
Hello,
I found a minor problem compiling memutil.lisp , because the
functions sb-kernel::copy-*-from-system-area aren't exported in the
latest version of sbcl.
I made a little patch to fix it.
Best Regards,
Leonardo Varuzza.
--
The most fundamental particles in this product are held tog
