Wolfgang Jenkner writes:
> James Amundson <amundson@users.sourceforge.net> writes:
>
> > On Thu, 2004-05-06 at 05:11, Andreas Eder wrote:
> >> Hi,
> >> is there still a lisp that we use for maxima, that cannot cope with
> >> the newer (?) situation names in eval-when?
> >
> > The question is whether the ANSI build of GCL 2.6.2 can cope with the
> > modern version of eval-when. I don't know the answer off the top of my
> > head.
> >
> > Unfortunately, in order to deal with the numerous warnings, you will
> > have to test things with GCL. Most of the non-standard forms are there
> > to support GCL. We only need to worry about 2.6.2 ANSI. (GCL 2.6.2 is
> > not quite released yet, but the current cvs 2.6.1 should be a very good
> > approximation of what 2.6.2 will be.)
>
> Actually, CVS ANSI GCL 2.7.0 seems to be the current version.
>
> I should add that if the great clean-up starts right now (which is
> fine with me) I'll apply my recently here announced no-legacy-packages
> patch before any other sweeping changes are likely to cause merge
> conflicts.
>
> Wolfgang
Ok, so I bit the bullet and installed ANSI GCL 2.7.0.
The good news is that the gcl build went fine and it seems to grok the
new eval-when situations just fine.
The I started a fresh maxima build for all of sbcl, cmucl, clisp and
gcl.
All went through fine except for gcl, that repeatedly break on compile
db.lisp with a strange error message:
Compiling /home/are/maxima/maxima/src/db.lisp.
Error in FUNCALL [or a callee]: Caught fatal error [memory may be damaged]
Fast links are on: do (use-fast-links nil) for debugging
Broken at DEFMODE. Type :H for Help.
1 (Continue) (SYSTEM:ERROR-SET
'(FUNCALL *MACROEXPAND-HOOK*
'#<compiled-function DEFMODE>
'(DEFMODE TYPE NIL
(ATOM (SELECTOR +LABS)
(SELECTOR -LABS)
(SELECTOR DATA))
SELECTOR)
'NIL))
2 Return to top level.
Maybe it has to do with the changes, but I can see no connection.
Can anyone shed more ligt on that?
Andres
--
Wherever I lay my .emacs, there's my $HOME.