> From: Sean Whitton <spwhit...@spwhitton.name> > Cc: debian-emacsen@lists.debian.org > Date: Mon, 24 Feb 2025 20:02:58 +0800 > > > On Mon 24 Feb 2025 at 07:42pm +08, Sean Whitton wrote: > > > The new Emacs 30.1 fails to build on all of Debian's 32-bit release > > architectures, Intel and Arm. > > > > The failures look a little different in each case but in all three the > > string "Pure Lisp storage overflow" appears near the end of the log: > > > > armel: > > https://buildd.debian.org/status/fetch.php?pkg=emacs&arch=armel&ver=1%3A30.1%2B1-1&stamp=1740392779&raw=0 > > armhf: > > https://buildd.debian.org/status/fetch.php?pkg=emacs&arch=armhf&ver=1%3A30.1%2B1-1&stamp=1740392697&raw=0 > > i386: > > https://buildd.debian.org/status/fetch.php?pkg=emacs&arch=armhf&ver=1%3A30.1%2B1-1&stamp=1740392697&raw=0 > > Xiyue pointed me to #75907 -- thank you. > > I can boost the BASE_PURESIZE just on Debian's builds but does it make > sense that we're hitting it sooner on 32-bit archs?
The actual use of pure space depends on the length of the file names involved in the build, so if you build in a deeper directory, it could overflow. Also, are you building the original release tarballs, and only with "configure && make -jN", or are you building using some different procedure? That could also explain the overflow. By how much do you need to enlarge to make the builds succeed?
