Re: [easybuild] GCCcore not setting environment variables?

[Maik Schmidt]

Hm, could this be related to having used --module-only? I found this:

https://github.com/easybuilders/easybuild-framework/issues/1877



Best,
Maik

Am 11.06.2018 um 10:41 schrieb Maik Schmidt:

but the environment variables in GCCcore are not mentioned there. So I guess this should have worked?

Hi all,









$ module load GCC
$ which gcc
/usr/bin/gcc



Best,

Maik

we're finally upgrading from RHEL6 to 7 and so I wanted to do fresh builds of most of our software using EasyBuild. Now, when trying to use the TensorFlow that I have built using the foss-toolchain, I got the error: ImportError: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /sw/installed/TensorFlow/1.8.0-foss-2018a-Python-3.6.4/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so) Apparently, it still uses the libstdc++.so from /usr instead of the one from the GCCcore module. I have looked at the module file, and to my surprise, I did not see it setting any environment variables like LD_LIBRARY_PATH at all. This cannot be intentional, right? It does not even set things like PATH or MANPATH, so a: still points to /usr, too. I've seen that in the gcc easyblock, there is the function "make_module_req_guess" that looks like it is supposed to handle those environment variables, but apparently, thoses "guesses" are not used anywhere. At least it doesn't end up in the module file for me... What am I missing here? Is this a bug?

--
Maik Schmidt
HPC Services

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Willers-Bau A116
D-01062 Dresden
Telefon: +49 351 463-32836

smime.p7s
Description: S/MIME Cryptographic Signature