[cells-gtk-devel] Compiling cells-gtk on SBCL
Ram Vedam
rvedam at gmail.com
Mon Jun 29 01:12:56 UTC 2009
Got it working! I guess I should have tried that first :) Thanks again
Ram
On Sun, Jun 28, 2009 at 4:12 PM, Ram Vedam <rvedam at gmail.com> wrote:
> Yes, I did modify test-gtk.lisp after a crazy longshot idea that it might
> be splitting the string into multiple arguments and passing each substring
> separately. Crazy idea I know... I'll try upgrading to SBCL 1.0.29 from
> 1.0.20 and see what happens. Thanks a lot for your help
> Ram
>
>
> On Sun, Jun 28, 2009 at 4:06 PM, Ramarren <ramarren at gmail.com> wrote:
>
>> Hello,
>>
>> This doesn't happen on my system, but there is something weird in the
>> log you sent:
>> Calling (gtk-window-set-title #.(SB-SYS:INT-SAP #X080EEDA8) Testing)
>> On my system is
>> Calling (gtk-window-set-title #.(SB-SYS:INT-SAP #X080CB640) GTK
>> Testing)
>> I wonder where the other part of the string went? Did you modify
>> test-gtk/test-gtk.lisp? It is given there as an initarg to test-gtk
>> app.
>>
>> Try erasing cells-gtk and all generated fasls, and redownloading and
>> recompiling, maybe something got stuck somewhere.
>>
>> Other than that this might be something to do with SBCL 1.0.20, which
>> is after all nine months old. I have tested only on current SBCL
>> 1.0.29, and just tried to running on CLISP. But I really don't know
>> how that would happen. Obscure memory access errors, maybe, but number
>> of arguments is just weird.
>>
>> Regards,
>> Jakub Higersberger
>>
>> On Sun, Jun 28, 2009 at 10:29 PM, Ram Vedam<rvedam at gmail.com> wrote:
>> > Hi
>> >
>> > I downloaded Jakub's code from git, got everything compiling and loaded
>> into
>> > my system fine, however when I run the test-gtk demo I get an invalid
>> number
>> > of arguments: 3 message from SBCL... Below is the stack trace I get when
>> I
>> > run the test-gtk demo with debug turned on.
>> >
>> > "----------UTILSRESET----------------------------------"
>> > eval (INIT-GTK)
>> > Calling (gtk-adds-g-thread-supported )
>> > (gtk-adds-g-thread-supported ) returns 1--> NIL
>> > eval (SHOW-WIN APP-NAME TERMINATE-ON-CLOSE T)
>> > eval (SETF APP (APPLY #'MAKE-INSTANCE APP-NAME VISIBLE (C-IN NIL)
>> INITARGS))
>> > Calling (gtk-accel-group-new )
>> > (gtk-accel-group-new ) returns #.(SB-SYS:INT-SAP #X080EF8C0)
>> > 0> NEW ID gtk-ffi:gtk-tooltips-new nil
>> > Calling (gtk-tooltips-new )
>> > (gtk-tooltips-new ) returns #.(SB-SYS:INT-SAP #X080B4B80)
>> > 0> WINDOW ADD KID nil notebook40
>> > 1> NEW ID gtk-ffi:gtk-window-new (0)
>> > Calling (gtk-window-new 0)
>> > (gtk-window-new 0) returns #.(SB-SYS:INT-SAP #X080EEDA8)
>> > 1> NEW ID gtk-ffi:gtk-notebook-new nil
>> > Calling (gtk-notebook-new )
>> > (gtk-notebook-new ) returns #.(SB-SYS:INT-SAP #X080EF000)
>> > Calling (gtk-container-add #.(SB-SYS:INT-SAP #X080EEDA8)
>> #.(SB-SYS:INT-SAP
>> > #X080EF000))
>> > (gtk-container-add #.(SB-SYS:INT-SAP #X080EEDA8) #.(SB-SYS:INT-SAP
>> > #X080EF000)) returns #.(SB-SYS:INT-SAP #X080915E8)
>> > Calling (gtk-widget-hide #.(SB-SYS:INT-SAP #X080EEDA8))
>> > (gtk-widget-hide #.(SB-SYS:INT-SAP #X080EEDA8)) returns NIL
>> > Calling (gtk-widget-set-sensitive #.(SB-SYS:INT-SAP #X080EEDA8) T)
>> > (gtk-widget-set-sensitive #.(SB-SYS:INT-SAP #X080EEDA8) T) returns NIL
>> > Calling (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080EEDA8) 650
>> 550)
>> > (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080EEDA8) 650 550)
>> > returns NIL
>> > Calling (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080EEDA8) 650
>> 550)
>> > (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080EEDA8) 650 550)
>> > returns NIL
>> > Calling (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080EEDA8) 650
>> 550)
>> > (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080EEDA8) 650 550)
>> > returns NIL
>> > Calling (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080EEDA8) 650
>> 550)
>> > (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080EEDA8) 650 550)
>> > returns NIL
>> > Calling (gtk-window-set-title #.(SB-SYS:INT-SAP #X080EEDA8) Testing)
>> > debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread #<THREAD
>> > "initial thread" RUNNING {A8345C1}>:
>> > invalid number of arguments: 3
>> >
>> > "----------UTILSRESET----------------------------------"
>> > eval (INIT-GTK)
>> > Calling (gtk-adds-g-thread-supported )
>> > (gtk-adds-g-thread-supported ) returns 0
>> > eval (PROGN (G-THREAD-INIT +C-NULL+) (GDK-THREADS-INIT))
>> > Calling (g-thread-init #.(SB-SYS:INT-SAP #X00000000))
>> > (g-thread-init #.(SB-SYS:INT-SAP #X00000000)) returns NIL
>> > Calling (gdk-threads-init )
>> > (gdk-threads-init ) returns NIL--> NIL
>> > eval (ASSERT (GTK-INIT-CHECK +C-NULL+ +C-NULL+))
>> > Calling (gtk-init-check #.(SB-SYS:INT-SAP #X00000000) #.(SB-SYS:INT-SAP
>> > #X00000000))
>> > (gtk-init-check #.(SB-SYS:INT-SAP #X00000000) #.(SB-SYS:INT-SAP
>> > #X00000000)) returns T--> NIL
>> > eval (GTK-INIT +C-NULL+ +C-NULL+)
>> > Calling (gtk-init #.(SB-SYS:INT-SAP #X00000000) #.(SB-SYS:INT-SAP
>> > #X00000000))
>> > (gtk-init #.(SB-SYS:INT-SAP #X00000000) #.(SB-SYS:INT-SAP #X00000000))
>> > returns NIL--> NIL
>> > eval (GTK-RESET)
>> > "----------UTILSRESET----------------------------------" --> #()
>> > --> #()
>> > eval (SHOW-WIN APP-NAME TERMINATE-ON-CLOSE T)
>> > eval (SETF APP (APPLY #'MAKE-INSTANCE APP-NAME VISIBLE (C-IN NIL)
>> INITARGS))
>> > Calling (gtk-accel-group-new )
>> > (gtk-accel-group-new ) returns #.(SB-SYS:INT-SAP #X080DDAE0)
>> > 0> NEW ID gtk-ffi:gtk-tooltips-new nil
>> > Calling (gtk-tooltips-new )
>> > (gtk-tooltips-new ) returns #.(SB-SYS:INT-SAP #X080B4840)
>> > 0> WINDOW ADD KID nil notebook4
>> > 1> NEW ID gtk-ffi:gtk-window-new (0)
>> > Calling (gtk-window-new 0)
>> > (gtk-window-new 0) returns #.(SB-SYS:INT-SAP #X080E60F0)
>> > 1> NEW ID gtk-ffi:gtk-notebook-new nil
>> > Calling (gtk-notebook-new )
>> > (gtk-notebook-new ) returns #.(SB-SYS:INT-SAP #X080EB800)
>> > Calling (gtk-container-add #.(SB-SYS:INT-SAP #X080E60F0)
>> #.(SB-SYS:INT-SAP
>> > #X080EB800))
>> > (gtk-container-add #.(SB-SYS:INT-SAP #X080E60F0) #.(SB-SYS:INT-SAP
>> > #X080EB800)) returns #.(SB-SYS:INT-SAP #X080915E8)
>> > Calling (gtk-widget-hide #.(SB-SYS:INT-SAP #X080E60F0))
>> > (gtk-widget-hide #.(SB-SYS:INT-SAP #X080E60F0)) returns NIL
>> > Calling (gtk-widget-set-sensitive #.(SB-SYS:INT-SAP #X080E60F0) T)
>> > (gtk-widget-set-sensitive #.(SB-SYS:INT-SAP #X080E60F0) T) returns NIL
>> > Calling (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080E60F0) 650
>> 550)
>> > (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080E60F0) 650 550)
>> > returns NIL
>> > Calling (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080E60F0) 650
>> 550)
>> > (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080E60F0) 650 550)
>> > returns NIL
>> > Calling (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080E60F0) 650
>> 550)
>> > (gtk-window-set-default-size #.(SB-SYS:INT-SAP #X080E60F0) 650 550)
>> > returns NIL
>> > Calling (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080E60F0) 650
>> 550)
>> > (gtk-widget-set-size-request #.(SB-SYS:INT-SAP #X080E60F0) 650 550)
>> > returns NIL
>> > Calling (gtk-window-set-title #.(SB-SYS:INT-SAP #X080E60F0) Testing)
>> > debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread #<THREAD
>> > "initial thread" RUNNING {A834701}>:
>> > invalid number of arguments: 3
>> >
>> > I was looking through the FFI section of code thinking that it might
>> have
>> > just been this function passing the arguments incorrectly to the
>> appropriate
>> > gtk function but the declaration matches the GTK documentation for it,
>> so I
>> > have no idea what might be causing this problem. Any thoughts?
>> >
>> > Ram
>> >
>> > On Fri, Jun 26, 2009 at 1:30 PM, Ramarren <ramarren at gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Cells-gtk optionally depends on cl-cairo2, which in turn depends on
>> >> trivial-features [ http://www.cliki.net/trivial-features ]. You can
>> >> either install it and all its dependencies, preferably using something
>> >> like http://common-lisp.net/project/clbuild/ , or you can disable it
>> >> if you don't need custom cairo drawing by editing features.lisp (same
>> >> about opengl extension).
>> >>
>> >> Regards,
>> >> Jakub Higersberger
>> >>
>> >> On Fri, Jun 26, 2009 at 8:00 PM, Ram Vedam<rvedam at gmail.com> wrote:
>> >> > I downloaded the version Ramarren mentioned on github last night, and
>> it
>> >> > was
>> >> > complaining about some package "TRIVIAL-FEATURES" associated with
>> >> > cl-cairo2.
>> >> > Has anyone else tried his branch of the cells-gtk code and if so,
>> have
>> >> > they
>> >> > also had the same problem or similar problems with cl-cairo2? If you
>> >> > need
>> >> > more info I'm running Ubuntu 8.10 on my box with SBCL 1.0.20
>> >> > Ram
>> >> >
>> >> > On Thu, Jun 25, 2009 at 12:31 AM, Ramarren <ramarren at gmail.com>
>> wrote:
>> >> >>
>> >> >> Did my message not go through? I shows in GMane, so I don't think it
>> >> >> was eaten by spam filters... anyway,
>> >> >> you are using a version of cells-gtk3 which is not compatible with
>> >> >> current CFFI. [I can tell by compiling order, compare
>> >> >>
>> >> >>
>> >> >>
>> http://github.com/Ramarren/cells-gtk3/blob/d2683cf228c2b8c868ea7a398bf961a32bc118ad/gtk-ffi/gtk-utilities.lisp
>> >> >> and
>> >> >>
>> >> >>
>> http://github.com/Ramarren/cells-gtk3/blob/b9d4d2badc5c7760c296fb9a67ade295c82119dd/gtk-ffi/gtk-utilities.lisp
>> >> >> . Not to mention the file-write date.]. You would either have to
>> >> >> downgrade all dependencies to their state from a year ago, or use my
>> >> >> update version from
>> http://github.com/Ramarren/cells-gtk3/tree/master
>> >> >> . Note the download button if you don't want to use git.
>> >> >>
>> >> >> On Thu, Jun 25, 2009 at 4:25 AM, Ram Vedam<rvedam at gmail.com> wrote:
>> >> >> > SBCL spits out the following when I tried to load cells-gtk3
>> >> >> >
>> >> >> > ;
>> >> >> >
>> >> >> >
>> >> >> >
>> /var/cache/common-lisp-controller/1000/sbcl/local/home/vedam/.sbcl/site/cells-gtk3/ph-maths/ph-maths.fasl
>> >> >> > written
>> >> >> > ; compilation finished in 0:00:00
>> >> >> > ; compiling file
>> >> >> > "/home/vedam/.sbcl/site/cells-gtk3/gtk-ffi/gtk-utilities.lisp"
>> >> >> > (written
>> >> >> > 03
>> >> >> > JUN 2008 11:33:41 AM):
>> >> >> > ; compiling (IN-PACKAGE :GTK-FFI)
>> >> >> > ; compiling (DEFUN GTK-SIGNAL-CONNECT ...)
>> >> >> > ; compiling (DEFUN G-SIGNAL-CONNECT-DATA ...)
>> >> >> > debugger invoked on a SB-KERNEL:CASE-FAILURE in thread #<THREAD
>> >> >> > "initial
>> >> >> > thread" RUNNING {A834699}>:
>> >> >> > #.(SB-SYS:INT-SAP #X00000000) fell through ETYPECASE expression.
>> >> >> > Wanted one of (CHARACTER SYMBOL INTEGER).
>> >> >> >
>> >> >> > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>> >> >> >
>> >> >> > restarts (invokable by number or by possibly-abbreviated name):
>> >> >> > 0: [TRY-RECOMPILING] Try recompiling gtk-utilities
>> >> >> > 1: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL
>> >> >> > {ABEEE41}>
>> >> >> > on
>> >> >> > #<ASDF:CL-SOURCE-FILE "gtk-utilities"
>> >> >> > {ABED4E1}>.
>> >> >> > 2: [ACCEPT ] Continue, treating #<ASDF:COMPILE-OP NIL
>> >> >> > {ABEEE41}>
>> >> >> > on
>> >> >> > #<ASDF:CL-SOURCE-FILE "gtk-utilities"
>> >> >> > {ABED4E1}>
>> >> >> > as
>> >> >> > having been successful.
>> >> >> > 3: [ABORT ] Exit debugger, returning to top level.
>> >> >> >
>> >> >> > Any ideas as to what might be wrong?
>> >> >> >
>> >> >> > Ram
>> >> >> >
>> >> >> > On Wed, Jun 24, 2009 at 1:48 PM, Peder Chr. Norgaard <pcn at pogt.dk
>> >
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> I myself went through a similar process half a year ago in the
>> >> >> >> Debian
>> >> >> >> unstable
>> >> >> >> context. I succeeded partially after tweaking some of the
>> >> >> >> components
>> >> >> >> really
>> >> >> >> hard - I never got the Drawing part to work. I have had the same
>> >> >> >> solution
>> >> >> >> working on a host of different SBCL versions.
>> >> >> >>
>> >> >> >> Now if you would could be just a little more concrete than
>> "having
>> >> >> >> trouble
>> >> >> >> compiling"/"looks like having trouble loading". What brand and
>> >> >> >> version
>> >> >> >> is
>> >> >> >> your operating system (cells-gtk depends on a lot more than
>> SBCL),
>> >> >> >> exactkt
>> >> >> >> what error message do you get at which step in the process... I
>> >> >> >> might
>> >> >> >> be
>> >> >> >> able to help you.
>> >> >> >>
>> >> >> >> But "having trouble compiling/loading" is not really helpful to
>> >> >> >> someone
>> >> >> >> who
>> >> >> >> wants to help!
>> >> >> >>
>> >> >> >> best regards
>> >> >> >> --peder chr.
>> >> >> >>
>> >> >> >> On Wednesday 24 June 2009, Ram Vedam wrote:
>> >> >> >> > Hi,
>> >> >> >> > I've been having trouble compiling cells-gtk on SBCL 1.0.20 .
>> From
>> >> >> >> > the
>> >> >> >> > looks of the error messages, it looks like its having trouble
>> >> >> >> > loading
>> >> >> >> > the
>> >> >> >> > GTK-FFI into my Lisp process but I'm not sure. I'm very new
>> with
>> >> >> >> > GTK
>> >> >> >> > (programmed Qt for a bit but not GTK) and I have never used
>> CFFI
>> >> >> >> > inside
>> >> >> >> > Common Lisp, so I'm not sure exactly what the problem is. Does
>> >> >> >> > anyone
>> >> >> >> > have
>> >> >> >> > any ideas?
>> >> >> >> >
>> >> >> >> > Ram
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Peder Chr. Nørgaard e-mail: pcn at pogt.dk
>> >> >> >> Gefionsvej 19
>> >> >> >> DK-8230 Åbyhøj tel: +45 87 44 11 99
>> >> >> >> Denmark mob: +45 30 91 84 31
>> >> >> >>
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> cells-gtk-devel site list
>> >> >> >> cells-gtk-devel at common-lisp.net
>> >> >> >> http://common-lisp.net/mailman/listinfo/cells-gtk-devel
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > cells-gtk-devel site list
>> >> >> > cells-gtk-devel at common-lisp.net
>> >> >> > http://common-lisp.net/mailman/listinfo/cells-gtk-devel
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cells-gtk-devel/attachments/20090628/afd896bf/attachment.html>
More information about the cells-gtk-devel
mailing list