On Mon, Apr 26, 2021 at 09:58:36AM -0400, Bone Baboon wrote: > `guix build --no-substitutes --cores=1 --max-jobs=1 webkitgtk` > `sudo guix system --no-substitutes --cores=1 --max-jobs=1 reconfigure > configuration.scm` > These two commands fail to build webkitgtk with the error message > reported previously. The problem being what you have identified (using > one core). > > `sudo guix system --no-substitutes reconfigure configuration.scm` > Fails to build webkitgtk because of what looks like an out of memory > issue. With "oom_reaper" showing up in /var/log/messages. > > `sudo guix system --no-substitutes --cores=2 --max-jobs=1 reconfigure > configuration.scm` > This command was successfully able to build webkitgtk.
Thanks for taking the time to perform all these builds; I'm sure they took a long time. I'm guessing that "--cores=2 --max-jobs=1" used fewer threads than the guix-daemon would normally choose by default on your computer? Like, maybe you have 4 cores / hyperthreads or something like that? It's unusual that a program requires multithreaded compilation, but I wonder if we can add a property to the package definition to require at least 2 threads when building.