- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After upgrading the Intel HPC Toolkit to the latest release 2024.2.0 on our Linux development server which runs CentOS 7 it turned out that the Intel Fortran Compiler 2024.2.0 now requires glibc 2.28:
/opt/intel/oneapi/compiler/2024.2/bin/compiler/xfortcom: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /opt/intel/oneapi/compiler/2024.2/bin/compiler/xfortcom)
Unfortunately, the latest glibc for CentOS 7 seems to be glibc version 2.17.
I tried to compile glibc version 2.18 from the GNU source for CentOS 7 but this resulted in a segmentation fault of the Intel Fortran Compiler when using the newly compiled glibc 2.18.
Is there any workaround available to use the latest Intel Fortran 2024.2.0 compiler with glibc 2.17 on CentOS 7.
Many thanks in advance for your advice.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Many years ago, I was in a similar situation and made the mistake of overwriting libc.so.6 with a newer version than the one installed in an attempt to provide the newer version to a newly installed software package that demanded it. The result was that even standard Linux/Unix utilities such as ls, chdir, etc., no longer worked, since almost everything on a modern Linux installation depends on libc.so.6. The only solution was to reinstall the OS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning, mecej4,
Thank you for your prompt response. I also tried to add a more recent version of glibc -- i.e. glibc 2.18 -- and I experienced the same flaws regarding standard Linux commands which did not work with glibc 2.18 any more.
Cheers,
Gusman
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I haven't tried this myself, but this may help https://gist.github.com/nchaigne/ad06bc867f911a3c0d32939f1e930a11
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning, Ron,
Thank you for your prompt response and for your kind advice to a newer version of GCC 9.2. This might definitely help. I will give it a try and then report how it works.
Cheers,
Gusman
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I installed GCC 9.2 on the CentOS 7 box and put the bin directory in front of the command search path and then called the Intel Fortran Compiler Version 2024.2.0, but the compiler still complains that it cannot find glibc version 2.18:
/opt/intel/oneapi/compiler/2024.2/bin/compiler/xfortcom: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /opt/intel/oneapi/compiler/2024.2/bin/compiler/xfortcom)
Thus, I compiled glibc version 2.18 using gcc 9.2 and appended the shared library directory to LD_LIBRARY_PATH. Now, the Fortran compiler crashes with a segmentation fault:
$ env LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/sw/glibc-2.18/lib /opt/intel/oneapi/mpi/latest/bin/mpiifx -diag-enable=all -qopenmp ../src/mpi_basic.f90 -o mpi_basic
Segmentation fault
Any hint how to resolve this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you know it's the compiler and not some other tool invoked by mpiifx? The compiler usually produces a more verbose error message when it segfaults.
![](/skins/images/D3C0B914909A6564BBB97F4AD1ED1973/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page