Closed shuds13 closed 3 months ago
@shuds13 The problem is the package sysroot_linux-64=2.12
, you need a newer version, at least 2.14
@minrk @jakirkham @leofang IIRC, this old sysroot comes from gfotran. Can you please remember me what's the proper recommendation for end users?
@dalcinl I updated sysroot_linux-64
on my local machine and this fixed this issue as you say.
However, it is curious that the default set up uses an old version and will probably trip up others. It looks like sysroot_linux-64
gets installed with gcc_linux-64
, which as far as I can tell comes from https://github.com/conda-forge/ctng-compiler-activation-feedstock. So perhaps I should raise an issue there.
If anyone, such as those pinged above, has a different recommendation for setting up the compilers in a conda environment, that would be very useful and good to document it here.
@dalcinl Not sure quite what their comment here means https://github.com/conda-forge/ctng-compiler-activation-feedstock/issues/123#issuecomment-2219158994
Maybe strong_constrains
can be used in the mpich build?
@shuds13 We are being told that the issue is fixed. Could you please try again?
@dalcinl Yes, it now works! This can be closed. Thanks.
Solution to issue cannot be found in the documentation.
Issue
With mpich 4.2.2, when using in a new conda environment, including on github actions, an undefined reference to GLIC 2.14 is reported. Even if a more recent version of glibc is present.
I don't know if there is a recommended way to ensure glibc matches in Conda, but this has never been an issue with previous versions (including mpich 4.2.1).
Steps to reproduce:
where helloworld_mpi.c is:
Note I have conda-forge channel.
Installed packages
Environment info