-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilers broken with undefined references to GLIBC_2.2.5 when installed on Rocky 9 OS #130
Comments
What's the output of I'm not sure what's going on. Any ideas, @minrk ? |
BTW, do this happen only with the Fortran compiler wrapper? Does the |
@dalcinl - The same issue is also present for the
I noticed that the environment output shows
And, of course, there is also the other problem that having to specify specific versions of |
Oh, and one other thing you might need to know... The
|
It appears that the compiler that gets installed in my
|
So the system compiler is OLDER than than the conda-forge compiler? That may be the root of all evil. @conda-forge/core I'm not sure what's the way to deal with these ABI issues. |
What's the output of |
And what's the output of |
|
|
Another thing I tried.... I noticed that the system I'm on has gcc version 12.2.0 installed via Spack and is available as an LMOD module. So, I tried loading it to change the default system version of GCC to more closely match the one in the conda environment.
This results in a different error:
I also tried completely deleting miniconda3 and reinstalling both it and my chiltepin environment while the |
Is there a way to reproduce this? Docker? |
It will take me some time, but I can try to make a Docker container that reproduces it. I'm not sure I'll be successful, but I can give it a shot. |
That's possibly related to
(since you have glibc 2.34, I don't know why it would fail to find a symbol that exists since 2.14) Out of curiosity, could you try installing |
That's a good observation.
It does not matter what is in the system while linking. It matter what's given to the linker. |
@h-vetinari / @isuruf - As suggested I added
This yields:
The
|
I see that there is a Rocky base image on docker hub with a version |
I have made some attempts to build a Docker container to reproduce the problem, but have not yet been successful. I was able to get a Rocky 9.1 (the machine I'm trying to debug has Rocky 9.1) container with miniconda3 installed. And I installed my environment using the same specs. The compiler wrapper works just fine in the container. However, I did observe some notable differences in the My machine:
My container:
I do not know why those are different. The |
I forgot to mention that the output of |
Do you have env variables like |
Yes.
|
Solution to issue cannot be found in the documentation.
Issue
Installing OpenMPI and wrappers with Miniconda3 on a Rocky 9 system results in compilers having GLIBC issues. Performing the exact same sequence of installation commands on an old CentOS 7 system works fine. A Spack installation of OpenMPI on the same Rocky 9 system also works just fine.
The environment installed:
Attempts to use
mpif90
result in the following:Attempts to use
mpicc
results in the same output, with a few additional undefined references:I tried
export OMPI_FC=$FC
, but it did not change the output.Installed packages
Environment info
The text was updated successfully, but these errors were encountered: