Treat mpi_family MPICH as MPICH 3.x instead of MPICH 1.x
Fix handling of MPICH 3.x for Scalasca 1.4.3

For Scalasca 1.x, there /is/ actually a difference between MPICH2 and
MPICH 3.x. The latter is only supported since Scalasca 1.4.3 (older
versions won't compile) and now correctly selected by the easyblock.
fotis@cern.ch

Signed-off-by: Fotis Georgatos <fotis@cern.ch>
2012-2014

Signed-off-by: Fotis Georgatos <fotis@cern.ch>
Uni.Lu/LCSB, NTUA

Signed-off-by: Fotis Georgatos <fotis@cern.ch>
fix easyblock headers

Signed-off-by: Fotis Georgatos <fotis@cern.ch>
Merge branch 'develop' of github.com:hpcugent/easybuild-easyblocks into bugfix_headers_fotis_cern_ch

- Yeah, I should have done it with rebase, however I have pushed in the repo already => tough luck :(
fix use of mpi_family() in ALADIN, Intel MKL and NWChem easyblocks, w.r.t. MPICH family
Merge pull request #521 from fgeorgatos/bugfix_headers_fotis_cern_ch

Bugfix headers fotis cern ch
use 'mpich2' value for ESMF_COMM with MPICH family (i.e., MPICH v3.x)
Fix typo
Merge pull request #519 from geimer/fix_mpich_inconsistencies

Treat mpi_family MPICH as MPICH 3.x instead of MPICH 1.x
chimera easyblock
added missing docstrings
changed depecrated imports
do cd using python
fixed typo
Merge pull request #524 from pescobar/Chimera

chimera easyblock
Merge branch 'develop' into fix_deprecated