[Bug-openmcl] problem compiling maxima

[Timothy Moore]

On Dec 10, 2003, at 12:05 AM, Gary Byers wrote:

>
>
> On Tue, 9 Dec 2003, Timothy Moore wrote:
>

> 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.
I sympathize, but this all seems to be handled automatically by 
configure and make. Panther at least seems to have the right versions 
of those tools.
>>> 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
>> so.
>>
>
> 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)
>
> macroexpands to:
>
> (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 ?
Yes, exactly. The macro works for me to in isolation, but after 
compiling around 30 files something seems to be corrupted.

Tim