At Sat, 6 Jan 2007 01:16:49 +0000 (UTC),
Luke Crook wrote:
>
> Samium Gromoff <[EMAIL PROTECTED]> writes:
>
> >
> > This fixes an apparent typo:
>
> Thank you Samium. What Lisp are you using that failed in the build? Both
> Lispworks and CLISP ignore this error.
I'm sorry for having had provided so little detail, it is probably too late
into the night...
The source is the latest SVN from sourceforge, built on SBCL 1.0.
the error log:
* (asdf:oos 'asdf:load-op 'lispbuilder-sdl)
[snip]
; compiling file "/mnt/etherstorm/exports/asdf/lispbuilder-sdl/cffi/syswm.lisp"
(written 02 JAN 2007 04:41:05 PM):
; compiling (IN-PACKAGE #:LISPBUILDER-SDL-CFFI)
; compiling (DEFCSTRUCT HWND__ ...)
; compiling (DEFCSTRUCT HGLRC__ ...)
; compiling (DEFCSTRUCT HDC__ ...)
; compiling (DEFCENUM SDL-SYSWM-TYPE ...)
; compiling (DEFCUNION SDL-SYS-WM-MSG-EVENT ...)
; compiling (DEFCSTRUCT SDL-SYS-WM-MSG ...)
debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread"
{A82F509}>:
Unknown CFFI type: SDL-SYS-WM-TYPE.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL {B452E59}> on
#<ASDF:CL-SOURCE-FILE "syswm" {B476AA1}>.
1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {B452E59}> on
#<ASDF:CL-SOURCE-FILE "syswm" {B476AA1}> as having been
successful.
2: [ABORT ] Exit debugger, returning to top level.
(CFFI::PARSE-TYPE SDL-SYS-WM-TYPE)
source:
; file: /mnt/etherstorm/exports/asdf/cffi/src/early-types.lisp
(ERROR "Unknown CFFI type: ~S." TYPE-SPEC-OR-NAME)
> - Luke
regards, Samium Gromoff
_______________________________________________
application-builder mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/application-builder
