I've just git pulled the latest version of cl-python and am getting the following build error:
<snip>
; compiling (YACC:DEFINE-PARSER *CL-YACC-PYTHON-PARSER* ...) ; compiling (DEFMETHOD LEXER-EOF-TOKEN ...) ; compiling (DEFMETHOD PARSE-FORM-WITH-YACC ...); compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 2660 (line 59, column 62) on #<SB-SYS:FD-STREAM for "file /home/jdn/work/lisp/cl-python/parser/grammar-clyacc.lisp" {1005DE4541}>: ; The symbol "YACC-EOF-SYMBOL" is not external in the YACC package. ; compilation aborted after 0:00:10.417
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL {1003130FA1}> on #<CL-SOURCE-FILE "grammar-clyacc" {100351D501}>. unhandled ASDF:COMPILE-FAILED in thread #<SB-THREAD:THREAD "initial thread" RUNNING {10029DDD71}>: erred while invoking #<COMPILE-OP NIL {1003130FA1}> on #<CL-SOURCE-FILE "grammar-clyacc" {100351D501}>
0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {1003F3F679}>)[:EXTERNAL] 1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000172DD1}>) 2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<ASDF:COMPILE-FAILED {1003E2B3C1}> #<unavailable argument>) 3: (INVOKE-DEBUGGER #<ASDF:COMPILE-FAILED {1003E2B3C1}>) 4: (ERROR ASDF:COMPILE-FAILED)[:EXTERNAL] 5: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE))
</snip>
Cheers, Jason
On Sat, Aug 8, 2009 at 1:20 AM, Jason Nielsenjdn@math.carleton.ca wrote:
I've just git pulled the latest version of cl-python and am getting the following build error:
Jason, thanks for still regularly checking the build. It's fixed now.
- Willem
On Sat, 8 Aug 2009, Willem Broekema wrote:
On Sat, Aug 8, 2009 at 1:20 AM, Jason Nielsenjdn@math.carleton.ca wrote:
I've just git pulled the latest version of cl-python and am getting the following build error:
Jason, thanks for still regularly checking the build. It's fixed now.
- Willem
Thanks for the fix. The build gets a little further along now but I still get the following error:
<snip> ; compiling file "/home/jdn/work/lisp/cl-python/core/metaclass.lisp" (written 07 AUG 2009 07:15:27 PM): ; compiling (IN-PACKAGE :CLPYTHON); compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 2925 (line 111, column 30) on #<SB-SYS:FD-STREAM for "file /home/jdn/work/lisp/cl-python/core/metaclass.lisp" {10052551F1}>: ; The symbol "DEFINE-HASH-TABLE-TEST" is not external in the SB-EXT package. ; compilation aborted after 0:00:00.005
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL {100333ED31}> on #<CL-SOURCE-FILE "metaclass" {1003340401}>. unhandled ASDF:COMPILE-FAILED in thread #<SB-THREAD:THREAD "initial thread" RUNNING {10029DDD71}>: erred while invoking #<COMPILE-OP NIL {100333ED31}> on #<CL-SOURCE-FILE "metaclass" {1003340401}>
0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {10052D0CF9}>)[:EXTERNAL] 1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000172DD1}>) 2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<ASDF:COMPILE-FAILED {10052C4A51}> #<unavailable argument>) 3: (INVOKE-DEBUGGER #<ASDF:COMPILE-FAILED {10052C4A51}>) 4: (ERROR ASDF:COMPILE-FAILED)[:EXTERNAL] 5: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) #<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL {100333ED31}> #<ASDF:CL-SOURCE-FILE "metaclass" {1003340401}>) </snip>
It has been on my to-do list to look deeper into the cl-python internals but I haven't got around to it. Sadly there are not enough hours in a day. Keep up the good work as cl-python is pretty cool.
Jason
On Sat, Aug 8, 2009 at 7:09 PM, Jason Nielsenjdn@math.carleton.ca wrote:
Thanks for the fix. The build gets a little further along now but I still get the following error:
; The symbol "DEFINE-HASH-TABLE-TEST" is not external in the SB-EXT package.
On May 21, 2009, SBCL changed it's custom hash table hash/test interface, and I assume you are using an earlier SBCL version. I only aim to support the most recent version of each implementation and library, unless there are compelling arguments to support a particular older version.
It has been on my to-do list to look deeper into the cl-python internals but I haven't got around to it. Sadly there are not enough hours in a day. Keep up the good work as cl-python is pretty cool.
Thanks for your continued interest, and let me know if there are things that are blocking you from using CLPython for some task it looks suitable for...
- Willem
clpython-devel@common-lisp.net