[Bug-openmcl] problem compiling maxima
gb at clozure.com
Tue Dec 9 16:05:04 MST 2003
On Tue, 9 Dec 2003, Timothy Moore wrote:
> This is with maxima from CVS and OpenMCL built from CVS (not bleeding
> edge) around November 26. I'm sorry that I haven't narrowed the problem
> down a bit; it is repeatable if you try to build all of maxima, but the
> actual failure is not repeatable in isolation.
> Check maxima out from
> :pserver:anonymous at cvs.sourceforge.net:/cvsroot/maxima
The sources I checked out apparently need to go through some
combination of autoconf/automake/whatever. On the rare occasions
that I remember what the magic incantations are, I usually discover
that I have the wrong versions of these things.
> ./configure --enable-openmcl
> make bootstrap
> (At some point in the make you end up at the top level prompt, due to a
> problem with the make rule; just type (quit))
> Eventually there will be an error:
> ; - Compiling source file "/Users/moore/maxima/src/mdebug.lisp"
> ;Compiling "/Users/moore/maxima/src/mdebug.lisp"...
> > Error in process listener(1): Unbound variable: ARGS
> > While executing: F
> > Type :GO to continue, :POP to abort.
> > If continued: Retry getting the value of ARGS.
> but a quick look at the macro in question (f) shows that this can't be
The version of maxima that I just checked out has a definition of F
in src/mdebug.lisp that looks like:
(defmacro f (op &rest args)
`(the fixnum (,op ,@ (mapcar #'(lambda (x) `(the fixnum ,x)) args) )))
and a call like:
(f + 1 2 3)
(THE FIXNUM (+ (THE FIXNUM 1) (THE FIXNUM 2) (THE FIXNUM 3)))
which seems to be what's intended.
> Let me know if I can provide more info,
Just to be sure that I understand: does it seem to be the case that
(somehow or other, in the environment in which maxima's being compiled)
things are somehow hosed to the point where this fails mysteriously,
even though in isolation it looks like a pretty simple macro ?
> Bug-openmcl mailing list
> Bug-openmcl at clozure.com
More information about the Bug-openmcl