On Wed, 16 Mar 2016, Camm Maguire wrote: > Greetings! Could you also please try changing the following line from > debian/rules: > > echo ':lisp (setq maxima::*maxima-started* nil si::*optimize-maximum-pages* t > si::*code-block-reserve* (make-array 10000000 :element-type (quote character) > :static t))(si::sgc-on nil)(si::gbc t)(si::save-system "foo")' | > ./maxima-local && mv foo src/binary-gcl/maxima > > > to > > echo ':lisp (setq maxima::*maxima-started* nil si::*optimize-maximum-pages* t > si::*code-block-reserve* (make-array 50000000 :element-type (quote character) > :static t))(si::sgc-on nil)(si::gbc t)(si::save-system "foo")' | > ./maxima-local && mv foo src/binary-gcl/maxima
Ok, tried today with the old configuration (5GB RAM + 2GB swap) using a swap file. The above change does not fix the build. The way it fails is the same as before: Error summary: Errors found in /build/MAXIMA/maxima-5.37.3/tests/rtest15.mac, problems: (47 49 55 61 67 73 79 85 91 165 174) Error found in /build/MAXIMA/maxima-5.37.3/tests/rtest8.mac, problem: (133) To summarize so far: A. It worked one month ago with only 2GB of RAM + 2 GB of swap. B. It fails with 5GB of RAM + 2 GB of swap. C. It works with 5GB of RAM + 3 GB of swap. Why more memory (from A to B) should make a program to fail is still a complete mystery to me. 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). 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. Thanks.
