Hi everyone!

For the port of OpenMusic to Linux, I took the version 0.51 of CLG and  
made some changes and added other bindings (like gtk-canvas), if you  
want to take a look at it, is here

http://sourceforge.net/projects/ircam-openmusic/

I named it 0.53, and it runs perfectly with the last cmucl.

Gerardo M. Sarria M.

------------------------------------------------------------------------ 
------------------

Le lundi, 3 nov 2003, � 15:34 Europe/Paris, Raymond Toy a �crit :

>
>>>>>> "Chisheng" == Chisheng Huang <[EMAIL PROTECTED]> writes:
>
>     Chisheng> Please fetch clg.tgz from  
> ftp://[EMAIL PROTECTED]
>     Chisheng> The password is sfsnash2.  This is based on CLG-0.51 by
>     Chisheng> Mr. Espen S. Johnsen with some hacks added by me.
>
> Got it.  On a different note, the configure script is broken for me
> with the latest CVS snapshot.  It doesn't find lisp.h, and doesn't
> figure out the fasl file extension correctly (sed errors).
>
> There are also a few errors.  First, I had to disable package locks
> because gforeign wants to redefine POINTER.  Something also wants to
> redefine the constant NULL.
>
> Anyway, everything seems to build ok.
>
>     Chisheng>        The second way:
>     Chisheng>          A. Fire up CMUCL
>     Chisheng>          B. (load "cmucl/cl-gtk.x86f")
>     Chisheng>          C. Type a number to get stack overflow.
>
> I tried this first, and a stack overflow does indeed occurr.  That's
> impossible. :-)  I don't understand how just loading a file can cause
> that to happen.  And typing anything into the repl causes a stack
> overflow.
>
>     Chisheng>        The first way:
>     Chisheng>          A. cd cmucl
>     Chisheng>          B. make test
>     Chisheng>          C. The above step will eventually invoke CMUCL.
>     Chisheng>             Type a number to get stack overflow.
>
> I tried this, and I get a nice window to pop up.  I clicked on one of
> the buttons, which popped up another window.  When I clicked the close
> button, I get a sigsegv in Lisp.
>
> My guess is that you have corrupted the lisp heap and that is causing
> the stack overflow, among other things.
>
> This will be probably be very difficult to track down unless you can
> find a smaller example that triggers it.
>
> Ray
>
> P.S.  I ran this all on Solaris, with GNOME 1.2 (or something).
> Configure said it was good enough.
>
>
>



Reply via email to