Re: Maxima cmucl patch



Greetings!

James Amundson <amundson@users.sourceforge.net> writes:

> On Tue, 2004-01-27 at 14:04, Vadim V. Zhytnikov wrote:
> > Hi!
> > 
> > James, could you take a look at the attached tiny
> > patch.  It assigns default value (lisp) to
> > CMUCL_RUNTIME if no other value is provided
> > by configure.  Without this patch configure/make
> > generate erroneous code for cmucl (else branch)
> > 
> > exec "$MAXIMA_VERPKGLIBDIR/binary-$MAXIMA_LISP/" -quiet -core ...
> > 
> > in maxima script if no --enable-cmucl is given.
> > 
> > I'm far for being automake/autoconf expert.  Is it sensible?
> 
> It's sensible, but it isn't quite the right thing to do. I'm sorry it
> has taken me so long to fix this bug. My source tree is in a confused
> state right now because I am in the middle of a fairly large change.
> (When I am done, windows builds without MinGW should be a reality...)
> 

Just curious about this one -- clisp on cygwin?  We are actually quite
close to a marked improvement of GCL on mingw.  I'm just wondering if
you'd feel a GCL port to cygwin would be desireable (should be
straightforward).  I've been told mingw is superior -- is there a
reason you are looking for a windows build without it?

Take care,

-- 
Camm Maguire			     			camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah