Greetings! Santiago Vila <sanv...@unex.es> writes:
> Ok, tried today with the old configuration (5GB RAM + 2GB swap) using > a swap file. > > The above change does not fix the build. > Thanks! In the built tree in this setup, could you please $ ls -l src/binary-gcl/maxima $ ./maxima-local (%i1) to_lisp(); MAXIMA> (length si::*code-block-reserve*) MAXIMA> (si::contiguous-report nil) MAXIMA> (setq *load-verbose* t) MAXIMA> (compile nil '(lambda nil nil)) > Could you please try on a machine with 5GB of RAM + 2 GB of swap? > (If you are not used to virtual machines, try virt-manager, it works great). I have a laptop and access to the debian build machines via ssh. I've installed virt-manager and looked at it briefly, but it appears to require root and or console access. I've got 4Gb on my laptop. > > In the meantime, I would suggest setting GCL_MEM_MULTIPLE=0.5 > somewhere in debian/rules. I have the feeling that the upstream > default of 1.0 is not a good one. > This should be harmless enough, but I suspect that the cure is accidental, i.e. the failure lies not in running out of memory but in placing code above the 2Gb limit. Thanks for your help in debugging this. Take care, -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
