Greetings, and thanks so much for the report!
Will attend to the installation issues ASAP.
The other is of course more serious. Since you have it all setup,
would you mind running with (si::use-fast-links nil)(trace (error
:entry (break))) and then do a :bt at the lisp prompt? For really low
level, build gcl with --enable-debug and catch the segfault under gdb.
If you do not have time, I understand. How do I get the source you
are working on?
Take care,
Waldek Hebisch <[EMAIL PROTECTED]> writes:
> > Greetings, and thanks so much for the feedback/report! This should be
> > fixed now. Releasing snapshot -70 to the Debian autobuilders...
> > Take care,
>
> ANSI version have build file, but it did not install the gcl command.
> Also, during 'compiler:link' I got error about missing
> '/var/tmp/hebisch/usrm/lib/gcl-2.7.0/unixport/../clcs/package.lisp'
> ('/var/tmp/hebisch/usrm/' is my prefix). It looks that copying
> 'gcl/clcs/package.lisp' by hand solved that problem.
>
> But later I hit another one: I am getting messages like:
>
> ;; Compiling stage0/ptyout.clisp.
> Segmentation violation: c stack ok:signalling errorError in error:
> ERROR TYPE-ERROR (DATUM #<FREE OBJECT 0000000001b5c888> EXPECTED-TYPE
> (OR METHOD-CALL FUNCTION)) NIL
>
> Backtrace:
>
> This is the first thing that the freshly linked image should do...
>
> --
> Waldek Hebisch
> [EMAIL PROTECTED]
>
>
>
--
Camm Maguire [EMAIL PROTECTED]
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
_______________________________________________
Gcl-devel mailing list
Gcl-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
