You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building an image that builds a gcc compiler (or any software depending on gmake) with older singularity versions (this issue happens at least up to 3.11.0, but doesn't at 3.11.4) through spack, the process will fail with an error of this type:
==> gcc: Executing phase: 'build'
==> Error: ProcessError: Command exited with status 2:
'/spack/opt/spack/linux-ubuntu22.04-zen3/gcc-11.4.0/gmake-4.4.1-wi55lxbbhsc647bu3c6qsoqf5guyuora/bin/make' '-j16' 'V=1'
1 error found in build log:
125 checking where to find the target windmc... host tool
126 checking whether to enable maintainer-specific portions of Makefiles... no
127 configure: creating ./config.status
128 config.status: creating Makefile
129 ==> gcc: Executing phase: 'build'
130 ==> [2023-09-22-16:28:27.773153] '/spack/opt/spack/linux-ubuntu22.04-zen3/gcc-11.4.0/gmake-4.4.1-wi55lxbbhsc647bu3c6qsoqf5guyuora/bin/make' '-j16' 'V=1'
>> 131 make: *** cannot open jobserver /tmp/GMfifo279169: No such file or directory. Stop.
See build log for details:
/root/.spack/stage/spack-stage-gcc-10.3.0-46nt4agntyurpc5u7wq7bh5odst6scvp/spack-build-out.txt
FATAL: While performing build: while running engine: exit status 1
This issue can be avoided by updating singularity to it's latest version. It can also be worked around by manually specifying to install the concerned program with the [email protected] dependency, in this case: spack install [email protected] ^[email protected]
The text was updated successfully, but these errors were encountered:
When building an image that builds a gcc compiler (or any software depending on gmake) with older singularity versions (this issue happens at least up to 3.11.0, but doesn't at 3.11.4) through spack, the process will fail with an error of this type:
This issue can be avoided by updating singularity to it's latest version. It can also be worked around by manually specifying to install the concerned program with the [email protected] dependency, in this case:
spack install [email protected] ^[email protected]
The text was updated successfully, but these errors were encountered: