Hi,
first, sorry for replying so late, but I'd like to give some feedback instead
of none ;-)
I'd see some good use for the following:
- c* ## clang-based toolchains are nice to combine together with the
--try-toolchain option; great to compare against goolf/foss builds
N.B. clang gives far better error messages than most other compilers. You
may wish to have it just for the build step.
- goolfc ## i'd lobby in favor of the gromacs builds against 1.4.10 & 2.6.10;
I'm not using it now but they serve well as CUDA-aware mockups
- iomkl/iompi ## these are the most cloud-friendly (in terms of licensing) for
those who do icc/ifort builds and wish to save cloud pennies
If you'd like to get rid of excess luggage, I'd deprecate most of their
easyconfigs but not the toolchains themselves.
More broadly, builds which took significant attention during our hackathons
(such as goolfc GROMACS builds) probably are a good keep.
FWIW: If I was in your shoes, I might consider keeping an HPL built for those
(in best-effort/experimental mode),
until the day it becomes a burden - because when so, then you *know* when/what
breaks, at the substrate.
In fact, it would be great service to the community, to expose the test cases
and logs done before any release!
ty! F.
--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
| sed 's/better bash/bash better/' # Yelling in a CERN forum
From: easybuild-requ...@lists.ugent.be [easybuild-requ...@lists.ugent.be] on
behalf of Kenneth Hoste [kenneth.ho...@ugent.be]
Sent: Thursday, September 01, 2016 14:59
To: easybuild@lists.ugent.be
Subject: [easybuild] deprecating of old/inactive toolchains
Dear EasyBuilders,
For the upcoming EasyBuild v3.0.0 (which will hopefully materialize
sometime in the coming months), we plan to deprecate a bunch of old and
inactive toolchains and toolchain versions.
All details, including what deprecation means exactly and why we are
doing is, are (for now) available on the following page on the EasyBuild
wiki: https://github.com/hpcugent/easybuild/wiki/Deprecated-toolchains .
Once we have settled on the list of toolchains to deprecate, I will move
that page to the official EasyBuild documentation at
http://easybuild.readthedocs.io .
I would like to ask you to take a quick look at the list of toolchains
we plan to deprecate; see
https://github.com/hpcugent/easybuild/wiki/Deprecated-toolchains#summary-of-toolchains-that-will-be-deprecated-in-easybuild-v300.
The current list of toolchains we plan to deprecate is included below,
but I will update the wiki page according to the provided feedback if
needed.
cgmpolf, cgoolf, cgmpich, cgmvapich2, cgompi, ClangGCC: all versions
gimkl and gimpi: (only) version 1.5.9
gmacml: (only) version 1.7.0
gmpolf and gmpich: (only) version 1.4.8
gmvolf + gmvapich2: (only) versions 1.7.12, 1.7.12rc1, 1.6.7, and 1.7.9a2
goalf: all versions (1.1.0-no-OFED, 1.5.12-no-OFED, 1.5.12)
goolf and gompi: (only) versions 1.4.10-no-OFED, 1.4.12-no-OFED,1.5.12,
and 1.5.14-no-OFED
goolfc, gompic, gcccuda: all versions (1.3.12, 1.4.10, 2.6.10)
gpsolf and gpsmpi: all versions (2014.12)
ictce and iimpi (+ matching iccfort versions): (only) versions 3.2.2.u3,
3.2.2.u3-32bit, 4.0.6, 4.0.10, 4.1.13, 5.1.1, 6.0.5, 6.3.5
iqacml + iiqmpi: all versions (3.3.0, 4.4.13)
intel-para + ipsmpi: all versions (2014.12)
iomkl + iompi: 4.6.13, 6.6.2, 6.6.4, 6.6.4-no-OFED
If you are still actively relying on any of these, please step forward
to let us know, so we can reconsider deprecating those particular
toolchains if needed.
Note that deprecating these toolchains does *not* (necessarily) mean
that easyconfigs using them will be broken in EasyBuild v3.0.0, only
that these easyconfigs will no longer be actively tested or maintained
in the future, and that they will not be available by default in future
EasyBuild releases.
regards,
Kenneth
