If possible, you can upgrade glibc with this patch: https://copr.fedorainfracloud.org/coprs/fweimer/glibc-rhel-7.5/ <https://copr.fedorainfracloud.org/coprs/fweimer/glibc-rhel-7.5/>
The other workaround is to set LD_BIND_NOW=1, but this kills SLURM. So, if you meet this bug, and are using slurm, try something like “srun --export=LD_BIND_NOW=1 ….” in your batch script. It solves the issue. dr. Alexandre Strube [email protected] Jülich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Jülich, Germany Phone: +49 2461 61-3866 Fax: +49 2461 61-6656 JSC is the coordinator of the John von Neumann Institute for Computing (NIC) and member of the Gauss Centre for Supercomputing (GCS) > On 13. Nov 2017, at 09:21, Paul Melis <[email protected]> wrote: > > A related link at intel, with references to relevant glibc bug reports, is > > https://software.intel.com/en-us/articles/intel-compiler-not-compatible-with-glibc-224-9-and-newer. > > I don't think this has caused issues at our place yet, but it's definitely > screwing up the plans for an update to RHEL 7.4 :-/ > > Paul > > On 12-11-17 20:59, Joachim Hein wrote: >> We got bitten by: >> https://software.intel.com/en-us/articles/inconsistent-program-behavior-on-red-hat-enterprise-linux-74-if-compiled-with-intel >> We are running CentOS 7.4. Many of our intel build apps are not working >> any longer. >> Best wishes >> Joachim >> Sent from my nanoPad > > > -- > > Paul Melis > | Visualization group leader & developer | SURFsara | > | Science Park 140 | 1098 XG Amsterdam | > | T 020 800 1312 | [email protected] | www.surfsara.nl |
signature.asc
Description: Message signed with OpenPGP
