[Ecls-list] how to build Ecl with preset higher memory bounds

Oliver Kullmann O.Kullmann at swansea.ac.uk
Sun Jan 23 19:49:28 UTC 2011


On Sun, Jan 23, 2011 at 01:40:16AM +0100, Juan Jose Garcia-Ripoll wrote:
> On Sat, Jan 22, 2011 at 8:14 PM, Oliver Kullmann
> <O.Kullmann at swansea.ac.uk>wrote:
> 
> > The information http://ecls.sourceforge.net/new-manual/ch20s03.html
> > I'm using already, but it doesn't work: It works from the (Maxima)
> > command-line
> > but not as an automated process, since then always some Lisp-process is
> > already
> > working, and Maxima segfaults
> >
> 
> Can you elaborate on this sentence? I do not understand the problem. When
> building Maxima using ECL's facilities you can specify statements that are
> going to be executed _before_ any Maxima code, thus effectively setting the
> limits for anything that will come later on
>

If I could pass information to Ecl when building Maxima
to the effect of setting the default memory-values, that
would be fine, but

1. All what I can find in Maxima-configure is

--with-ecl=$(ecl_call_okl) --enable-ecl

(and that I'm using already).

Nothing mentioned about influencing calling Ecl.

2. Even if I could pass something to Ecl (I could write
a wrapper around the Ecl program), then I wouldn't know
what to pass, since as far as I can see, only run-time
information is passed, that is, setting memory-values should
only be valid for that single invocation?


Alternatively, passing options to Ecl via Maxima apparently doesn't
work:

If I call maxima with

--lisp-options="-frame-stack=4096"

or

--lisp-options="-frame-stack 4096"

or using "--frame-stack" ... no effect at all (at http://ecls.sourceforge.net/new-manual/ch17s02.html
there is no information on how to use command-line arguments) ?


Is it really so difficult to just change the Ecl-source?
I searched around in the source-code, but couldn't find it.

Oliver





More information about the ecl-devel mailing list