Issue with apps having ncurses as dependency

[theklaloizou]

Hi all,

We have a pipeline where we build applications inside Rocky 8 singularity containers. Currently we are facing an issue when trying to build gettext-0.21.1 or any other packages that has as dependency a version of ncurses that is not already installed on the cluster. We are using SLURM and we build applications as jobs on the cluster. The problem is that if we try to build gettext-0.21.1 we first need to build ncurses 6.3 which is a dependency. If we build them both on the same node, ncurses is being built successfully but gettext is failing during configure step when config.guess script is being ran by ConfigureMake easyblock with the error:

"config.guess" exited with exit code 127 and output:
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 535: elf_machine_rela_relative: Assertion ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!

If we build ncurses and gettext on two separated nodes we don't face this issue. Any ideas what might be causing it?

[Micket]

This seems bizarre, but also raises a lot of questions:

1. in both cases, I assume ncurses is built to completion first, so, it's just a question of whether you tried building gettext on the same or different node afterwards?
2. You are not building anything as root i hope?
3. surely these are building against some network attached storage? If the 1. is true here, i really struggle to see how the node can matter, as nothing should touch the node itself.