BUG: Currently, on line 1351 of reproduce/software/shell/configure.sh in commit 8161194, the available space required for /dev/shm to be accepted for usage is hardwired to 2Gb. However, at least gcc requires increasingly greater amounts of temporary disk space with each major version upgrade, and high-level user package might require lots of disk space. This should be set as a configurable parameter in an obvious place, so that when either maneage is updated or a science project has a big package added, the requirement is appropriately modified.

DETAILS:
Line 1351 of reproduce/software/shell/configure.sh in commit 8161194:

  1348  if [ x"$shmdir" != x ]; then
  1349
  1350      # Make sure it has enough space.
  1351      needed_space=2000000
  1352      available_space=$(df "$shmdir" | awk 'NR==2{print $4}')
  1353      if [ $available_space -gt $needed_space ]; then
  1354

Maneage 8161194 has gcc version 12.1.0 . I've only done a quick analysis, but "disk" usage (on a ram disk) did go up to 7.4 Gb based on checking each 30 seconds (a short spike could have gone higher):

.../build/software/build-tmp$ du -sh .
7.4G    .

In principle, a computer that only allows 2Gb of RAM will fail for commit 8161194.

SUGGESTED FIX:
1. The 'needed_space' value should be configurable in a place that is natural and obvious, so that both people upgrading maneage and people adapting it for their particular project will easily find it, e.g. reproduce/software/config/shared_memory.conf .

2. A note should be placed in reproduce/software/config/versions.conf immediately above the gcc entry warning that the 'needed_space' value may have to be increased (or might be decreasable if downgrading to an older gcc).

A short-term fix should at least change the hardwired value to a value that is enough for gcc-12.1.0, e.g. 8000000.