Greetings! I cannot reproduce this with latest maxima cvs and gcl
2.6.1-38. Do you have a non-standard db.lisp lying around somewhere?
Take care,
Andreas.Eder@t-online.de (Andreas Eder) writes:
> James Amundson writes:
> > On Thu, 2004-05-06 at 17:32, Andreas Eder wrote:
> > > Wolfgang Jenkner writes:
> >
> > > > Actually, CVS ANSI GCL 2.7.0 seems to be the current version.
> >
> > > Ok, so I bit the bullet and installed ANSI GCL 2.7.0.
> >
> > On Thu, 2004-05-06 at 18:34, Billinghurst, David (CALCRTS) wrote:
> >
> > > Actually the first statment is correct. gcl-2.6.2 will be released shortly.
> > > gcl-2.7.0 is the development branch.
> >
> > David is right. GCL 2.6.2 is the upcoming release in the stable branch.
> > We should not rely on features that are only in the development branch
> > (2.7.0). It is particularly important to have the correct version of
> > GCL, because ANSI-compliance issues are changing rapidly.
> >
> > --Jim
> >
>
>
> Well, I installed ANSI GCL 2.6.1-38 and unfortunately it shows the
> same error as 2.7.0. Compilation bails out at db.lisp with
> Error in FUNCALL [or a callee]: Caught fatal error [memory may be
> damaged]
>
> Maybe someone more knowledgeable than me should have a look at that
> because as far as I see (according to the documentation) GCL should
> grok the new situation names.
>
> Andreas
> --
> Wherever I lay my .emacs, there's my $HOME.
>
> _______________________________________________
> Maxima mailing list
> Maxima@www.math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
>
>
>
--
Camm Maguire camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah