FYI, there are newer goolf and foss in the 'devel' tree.
gompi/goolf-1.7.20 with GCC 4.8.4 and OpenMPI 1.8.4 gompi/foss-2015a with GCC 4.9.2 and OpenMPI 1.8.4 As for predicting what future numbers will be used by EB... good luck. 8^) They have rough heuristic that used to be used. Very rough. Personally, here at TAMU where I am creating toolchains for the IBM XL compilers, I've just gone to using a time stamp. e.g. xlompi-215.1.1.447 - XL compiler on top of GCC 4.4.7 with OpenMPI 1.8.4 xlmpich-2015.1.1.484 - XL compiler on top of GCC 4.8.4 with MPICH 3.1.3 xlmpich2-2015.1.1.492 - XL compiler on top of GCC 4.9.2 with MPICH2 1.5 xlmvapich-2015.1.1.484 - XL compiler on top of GCC 4.8.4 with MVAPICH 1.9 I figure when it comes time to bump the XL or MPI version number I'll just use the date at that time (e.g a new toolchain today would have 2015.3.6[.gccver] as a version). Just my $.02. jack On 03/06/2015 08:46 AM, Timothy Brown wrote:
Hi, I've been trying to roll out EasyBuild and Lmod here (University of Colorado, Boulder) and have managed to do the hard sell to most people. I'm in the process of converting our 500+ hand built programs and tcl module files. Thanks for providing such a good framework! I was wondering how you do the version numbering of the toolchains? As I am updating the gompi and goolf ones for GCC 4.9.2 and OpenMPI 1.8.4. Currently gompi 1.6.10: - GCC 4.8.2 - OpenMPI 1.7.3 I know I can pick whatever numbers I want, however I'd like to pick the "right" ones so I could possibly - avoid confusion when the easy configs get update to include these versions. - possible contribute back upstream. Any thoughts, ideas or hints? Thanks once again! Timothy
