Greetings! One other debugging idea in case you are interested/motivated: as the package is building in one terminal, open another, change to the build directory, and
GCL_MULTIPROCESS_MEMORY_POOL=$(pwd) gcl27 >(si::pool-watch 3 300000) This will list the number of processes and total pages allocated, which should match your measurements from other system tools. Take care, Santiago Vila <[email protected]> writes: > On Tue, May 05, 2026 at 01:41:29PM +0200, Santiago Vila wrote: > >> I did not try a second time, but it looks like the same problem, which means >> this is not really loong64-specific and maybe you can also reproduce >> the problem more easily on amd64 using the GRUB_CMDLINE_LINUX="nr_cpus=1" >> trick. > > Nevermind. Maybe this is just trying to use more memory than available. > > My single-cpu system had 16 GB of RAM and some swap. Monitoring Committed_AS > in /proc/meminfo tells me it was trying to allocate 18 GB of RAM. > > On systems with 2 CPUs, I know that it tries to allocate 27 GB of RAM. > > This is a problem not only for buildd.debian.org but also for anybody > trying to do QA. I see the package is blacklisted here: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/acl2.html > > I guess reproducible-builds people would definitely prefer not having to > blacklist it. > > Thanks. > > > -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
