Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2435.golett.os - Linux centos linux 7.4.1708, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, Python 2.7.5
See https://gist.github.com/afc183551481f53ecc26c1eb386c40d9 for a full test report.

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2065.delcatty.os - Linux centos linux 7.4.1708, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/1b8353602d755d45d60e8e4671ed82a4 for a full test report.

fails on CentOS 6.x because #6345 requires GLIBC_2.14

(also, uploading the test report from this one fails due to an encoding problem, see https://gist.github.com/migueldiascosta/16deb3166076fbac3e18e8e3dacd5d56)

@migueldiascosta Since the dotNET runtime is a binary install, there's little we can do about this I think... Other than providing our own glibc maybe, but that should be done way deep down the stack (under binutils & GCCcore).

@boegel our own glibc would be good for other reasons (e.g., libmvec), but in this particular case, maybe the name should give a hint it will not work in older distributions? (e.g. there are a couple of centos6/centos7 easyconfigs)

at the very least, a comment

@migueldiascosta Using our own glibc is also a nice can of worms in practice, since it will likely result in problems elsewhere...

For now, I think a comment to clarify the implicit dependency on a recent glibc is sufficient (who still uses CentOS 6.x anyway ;-)).

@boegel touché :)

Going in, thanks @boegel!