Automatic reply from Jenkins: Can I test this?

Test report by @geimer
SUCCESS
Build succeeded for 37 out of 37 (38 easyconfigs in this PR)
Linux debian 7.8, Intel(R) Xeon(R) CPU X5550 @ 2.67GHz, Python 2.7.3
See https://gist.github.com/24af3631d131353b314c for a full test report.

Test report by @geimer
SUCCESS
Build succeeded for 38 out of 38 (38 easyconfigs in this PR)
Linux debian 7.8, Intel(R) Xeon(R) CPU X5550 @ 2.67GHz, Python 2.7.3
See https://gist.github.com/53f7d3a7aa77f703fed8 for a full test report.

Now with the installed GCC included ;-)

Jenkins: ok to test

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/2294/
Test PASSed.

Well, checksum verification actually takes place immediately before extracting the source archive. Thus, the tests above didn't verify the checksums. Trying again with --stop=source...

Test report by @geimer
SUCCESS
Build succeeded for 38 out of 38 (38 easyconfigs in this PR)
Linux debian 7.8, Intel(R) Xeon(R) CPU X5550 @ 2.67GHz, Python 2.7.3
See https://gist.github.com/97793b675028f13637b2 for a full test report.

Test report by @boegel
SUCCESS
Build succeeded for 38 out of 38 (38 easyconfigs in this PR)
Linux SL 6.6, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.6
See https://gist.github.com/672968447159f7c876d0 for a full test report.

Looking excellent, thanks a lot for looking into this @geimer!