> 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))
I'll try. > > 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. Yes, you have to be root to setup the thing initially, certainly not to be done on a Debian official machine. I'm afraid that 4 GB of RAM will not be enough to reproduce this. Let me think what we can do about this. > > 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. To be frank, I don't think that using GCL_MEM_MULTIPLE is a good solution either. When testing for "dpkg-buildpackage -A", I found that I always need more and more memory, so I setup a "memory monitor" to see how much memory does a package uses exactly. If a given package uses all available memory, no matter what, my memory monitoring system will tell me that it needs 4GB on a 4GB machine, 8GB on a 8GB machine, and so on. I would much prefer that packages use the memory they really need, regardless of the memory of the system on which the package is built. Thanks.
