Hi Ken, On Mar 29, 2013, at 6:12 PM, Kenneth Hoste wrote: > The first release candidate for EasyBuild v1.3.0 is now available through the > v1.3.x (and v1.3.0.x) branches on GitHub. > > To install EasyBuild v1.3.0rc1, use something like: > > easy_install --prefix=$HOME/.local > http://github.com/hpcugent/easybuild-easyconfigs/archive/v1.3.0.x.tar.gz > easy_install --prefix=$HOME/.local > http://github.com/hpcugent/easybuild-easyblocks/archive/v1.3.x.tar.gz > easy_install --prefix=$HOME/.local > http://github.com/hpcugent/easybuild-framework/archive/v1.3.x.tar.gz
Instead of trying the new goolf toolchain - which OK, I will eventually do - I happened to have gone in another productive direction instead: Playing with the intel compiler toolchains v5.2.0 & v5.3.0, as per 2 dirs visible here: https://github.com/fgeorgatos/easybuild.experimental/tree/master/users/fgeorgatos fyi. Combining the latter of these with v1.3.0rc2 yielded, so far, >150 modulefiles without any major effort; see below for a crude first report. In short, the last version feels stable - at least as regards this toolchain. N.B. v5.3.0 toolchain includes the upstream components that were announced just this morning from Intel... well done to all! I issued #194 Pull Request now :) I took the freedom to baptize v5.3.0, feel free to modify that, if so desired. > PS: The CUDA support we hoped to include in EasyBuild v1.3.0 has been delayed > to a future release, mainly due to time constraints. This is not so bad as it sounds: * CUDA toolchain *IS* now included, only the combo goolfc toolchain is missing; fyi. Adam's advice has helped us produce quite decent CUDA support, we just need to "packetize" it in toolchain now so that it is of generic use for composite builds. fi. the 1st file seen in PR #165, should do the right thing (TM) or, it used to ;-) ps1. shouldn't the version suffix of CUDA be reflected in the filename? ps2. we have quite a few lib* packages that ended up in "devel" category... let's fix it? enjoy, Fotis
