headers
Keith James | 12 Dec 2008 15:54
Picon

Compile failure on SBCL 1.0.22

Hi,

I'm looking at PowerLoom to provide ontology-based reasoning for my Common 
Lisp bioinformatics applications. I'm getting a type error when compiling on 
SBCL.

Powerloom 3.2.0

CL-USER> (list (lisp-implementation-version) (machine-type))
("1.0.22" "X86")

In primal.lisp

Cannot set SYMBOL-VALUE of STELLA::*HASH-BYTE-RANDOM-TABLE* to :NULL_VALUE 
(not of type SIMPLE-VECTOR.)
   [Condition of type SIMPLE-TYPE-ERROR]

Restarts:
 0: [RETRY] Retry SLIME REPL evaluation request.
 1: [ABORT] Return to SLIME's top level.
 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING 
{AB670F9}>)

Backtrace:
  0: (SB-INT:ABOUT-TO-MODIFY-SYMBOL-VALUE 
STELLA::*HASH-BYTE-RANDOM-TABLE* "set SYMBOL-VALUE of ~S" :NULL_VALUE)
  1: (SET STELLA::*HASH-BYTE-RANDOM-TABLE* :NULL_VALUE)
  2: (SB-IMPL::%DEFVAR ..)

In literals.lisp
(Continue reading)

Permalink | Reply | 3 comments |
headers
Thomas Russ | 12 Dec 2008 19:03
Picon
Favicon

Re: Compile failure on SBCL 1.0.22


On Dec 12, 2008, at 6:54 AM, Keith James wrote:

> Hi,
>
> I'm looking at PowerLoom to provide ontology-based reasoning for my  
> Common
> Lisp bioinformatics applications. I'm getting a type error when  
> compiling on
> SBCL.
>
> Powerloom 3.2.0

You should use the most recent snapshot.  A lot of bug fixes have gone  
in since our last official release.  In particular, there were a  
number of changes to make PowerLoom work with the stricter type  
inference and enforcement of SBCL and CMUCL.

The current snapshot compiles for me with SBCL 1.0.12 (I haven't  
upgraded in a while).

>
>
> CL-USER> (list (lisp-implementation-version) (machine-type))
> ("1.0.22" "X86")
>
> In primal.lisp
>
> Cannot set SYMBOL-VALUE of STELLA::*HASH-BYTE-RANDOM-TABLE*  
> to :NULL_VALUE
(Continue reading)

Permalink | Reply | 2 comments |
headers
Keith James | 12 Dec 2008 21:28
Picon

Re: Compile failure on SBCL 1.0.22

On Friday 12 December 2008 18:03:52 Thomas Russ wrote:
> You should use the most recent snapshot.  A lot of bug fixes have gone
> in since our last official release.  In particular, there were a
> number of changes to make PowerLoom work with the stricter type
> inference and enforcement of SBCL and CMUCL.
>
> The current snapshot compiles for me with SBCL 1.0.12 (I haven't
> upgraded in a while).
>
> > CL-USER> (list (lisp-implementation-version) (machine-type))
> > ("1.0.22" "X86")

Thanks for the quick reply. I experience the same errors with the 3.2.38 
snapshot.

I'm unable to backup to an older SBCL, so I've set 
*stella-compiler-optimization* to a higher debug level and rebuilt so that I 
can have a look around.

(Incidentally, I get a clean build with CMUCL 19e.)

--

-- 
Keith
Permalink | Reply | 1 comment |
headers
Thomas Russ | 12 Dec 2008 23:07
Picon
Favicon

Re: Compile failure on SBCL 1.0.22


On Dec 12, 2008, at 12:28 PM, Keith James wrote:

> On Friday 12 December 2008 18:03:52 Thomas Russ wrote:
>> You should use the most recent snapshot.  A lot of bug fixes have  
>> gone
>> in since our last official release.  In particular, there were a
>> number of changes to make PowerLoom work with the stricter type
>> inference and enforcement of SBCL and CMUCL.
>>
>> The current snapshot compiles for me with SBCL 1.0.12 (I haven't
>> upgraded in a while).
>>
>>> CL-USER> (list (lisp-implementation-version) (machine-type))
>>> ("1.0.22" "X86")
>
> Thanks for the quick reply. I experience the same errors with the  
> 3.2.38
> snapshot.
>
> I'm unable to backup to an older SBCL, so I've set
> *stella-compiler-optimization* to a higher debug level and rebuilt  
> so that I
> can have a look around.

OK.  I downloaded the 1.0.22 version of SBCL and ran into the same  
problem.
There seems to be a bug in our translator, in that it isn't producing  
the correct value.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane