You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perused open issues, however, did not see this specific issue. I apologize if this is a duplicate...
Also, cl-gtk4 states to be compatible with implementations that have support for CFFI callback (required by `cl-gobject-introspection'), though unsure if it is an issue with their implementation or clasp's.
Expected behavior
Loads system successfully, analogously to what is observed for SBCL.
Actual behavior
When loading system :cl-gtk4/example, clasp errors with the following message:
Condition of type: TYPE-ERROR
NIL is not of type LLVM-SYS:IRBUILDER-BASE.
Code at issue
Note: Using Guix SD, so cl-gtk4 dependencies are installed via manifest specifying dependencies as opposed to quicklisp.
Describe the bug
Loading example system from
cl-gtk4
(https://github.com/bohonghuang/cl-gtk4/tree/master/examples) results in TYPE-ERROR.Perused open issues, however, did not see this specific issue. I apologize if this is a duplicate...
Also,
cl-gtk4
states to be compatible with implementations that have support for CFFI callback (required by `cl-gobject-introspection'), though unsure if it is an issue with their implementation or clasp's.Expected behavior
Loads system successfully, analogously to what is observed for SBCL.
Actual behavior
When loading system
:cl-gtk4/example
, clasp errors with the following message:Code at issue
Note: Using Guix SD, so
cl-gtk4
dependencies are installed via manifest specifying dependencies as opposed to quicklisp.Guix Manifest used (
gtk4-manifest.scm
):Code that results in error (in clasp):
Code above trialed for SBCL loads successfully and is able to subsequently run example
(gtk4.example:simple-menu)
Other steps to reproduce
~/common-lisp
or another asdf loadable locationguix shell -m path/to/gtk4-manifest.scm -- clasp
(source listed above)Context
The text was updated successfully, but these errors were encountered: