Hi Nick, On Dec 23, 2015, at 9:01 PM, Nick Vandewiele <[email protected]> wrote: > Is there a way to specify a compiler toolchain without the requirements to > specify its exact version number? The idea would be that some software is > robust enough to accept whatever version of a toolchain is available. Or is > this too unrealistic to imagine?
If understand well what you are trying to do, it boils down to 2 steps: * implement some form of toolchain (alike ictce, intel, goolf - whatever has a good collection of the related APIs, roughly: compilers+mpi+MKL) * Use recursive builds of a software, for building against that toolchain, fi. eb —try-toolchain=myintel,8.8.8 Python-2.7.3-intel-6.0.0.eb -r When you have done the homework well for the first step, the 2nd step is just magic - sit back, relax, make coffees, it all builds nicely. Of course, it’s not all roses. You really need to master the toolchain generation step well, presumably based upon your icc-system.eb; you will need to spend some time with it, my advice would be to only replace a piece at a time and see if/how things break. It is entirely possible that you will need to patch existing easyblocks, in order to overcome minor diffs; it happens all the time. Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
