-
Notifications
You must be signed in to change notification settings - Fork 699
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
intel/2014.11 and intel/2014.10 toolchains #1219
Conversation
toolchain = {'name': 'dummy', 'version': 'dummy'} | ||
|
||
suff = '0.090' | ||
compver = '2015.%s' % suff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for a 'standard' toolchain, we probably don't want to jump in with a new major version of the Intel compilers... been there, never again
@wpoely86: I understand you're proposing this since that is what is needed for C++11 support?
@gjbex/@hpcleuven, @hajgato, @sbecuwe: thoughts on this? |
Test PASSed. |
Well, If we go for 2015, then I would go for 2015.1.133 (2015 update 1)for C/C++/Fortran, 11.2.1.133 for MKL and 5.0.2.044 (5.0 update 2) for MPI. |
easyblock = "Toolchain" | ||
|
||
name = 'intel' | ||
version = '2015a' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change to 2014.12
, so we can be more conservative with 2015a
(no 2015 compilers yet)
add intel 2014.11 definition + required easyconfigs
Test FAILed. |
Test FAILed. |
Jenkins: test this please |
Test PASSed. |
@wpoely86: let's add an HPL easyconfig for both toolchains, so we can test an installation on top of this toolchain too? |
@boegel done, ready for merge? |
Test PASSed. |
Test report by @boegel |
Looks great, going in. Thanks @wpoely86! |
intel/2014.11 and intel/2014.10 toolchains
This is a proposal for a
intel-2015a
toolchain. This toolchain will work for C++11 code.