Hi Erik,
On 05/07/16 16:08, Erik Smeets wrote:
Hi Kenneth,
-----Original Message-----
It seems like you may be filtering binutils from the dependencies (via --filter-
deps), see also https://github.com/hpcugent/easybuild-
framework/issues/1494...
Thanks, I think it was caused by an old modulesenvironment binutils version
(outside of EB) which was clashing with EB. This was removed and now it seems
to work fine.
Yes, that sounds like the likely cause, see also
https://github.com/hpcugent/easybuild-framework/issues/1385 .
For foss/2016b update we are jumping to GCC 5.4, cfr.
https://github.com/hpcugent/easybuild-easyconfigs/pull/3271.
GCC 4.9.x is getting quite old (4.9.0 was released April 2014, latest
4.9.3 is from June 2015, cfr. https://gcc.gnu.org/develop.html#timeline).
Then what's going to be the difference between foss-2016b and foss-2016.06 and
why keep two toolchains that are the same besides the naming scheme?
foss/2016.06 was sort of a trial toolchain for foss/2016b; they're
identical except for the version of LAPACK (3.6.1 vs 3.6.0), since a new
LAPACK version was released shortly before foss/2016b was cast into stone.
The intention of the foss & intel toolchains that are versioned using
<year>(a|b) is that they're 'common' toolchains, i.e. stable well-tested
toolchains that multiple sites can pick up and create easyconfigs for,
to sort of channel the efforts.
The idea is to revise them every 6 months, but additional versions may
be defined in between, either because of particular reasons (e.g.
different GCC version) or as a trial for an upcoming update of the
common toolchains.
regards,
Kenneth
