Sorry for bringing this topic to live again. I have a CentOS 7 system where the default libstdc++.so.6 is NOT providing the CXXABI_1.3.8. This I found out by executing ‘strings libstdc++.so.6 | grep CXXABI’ at the prompt. However, I do have a conda environment, which is activated, that wants to access the CXXABI_1.3.8 and points to /usr/lib64/libstdc++.so.6 instead of its own /opt/anaconda3/envs/cuda10_base/lib/libstdc++.so.6 or the eqv. /opt/anaconda3/envs/cuda10_base/x86_64-conda_cos6-linux-gnu/sysroot/lib/libstdc++.so.6. These instances do indeed provide CXXABI_1.3.8 as they should.
Does this imply that links are broken in conda? Why is the conda environment not looking in the correct place? And what can I do about it without “destroying” my sym-links in the CentOS-system? Also, it could explain the above users experience also.
Kind regards, Per v R