Hi Valeriu, On Nov 21, 2014, at 2:14 PM, Valeriu Codreanu <[email protected]> wrote: > However, in order to deploy it on our system I need to know a few extra > things: > • We currently have a lot of software modules already installed. We > would prefer if possible to not rebuild every module with EasyBuild, but > re-use some of the existing modules (e.g. Intel Compilers) when building > other libraries/applications through EasyBuild. Do you have a procedure for > achieving this?
Assuming that your pre-existing modules may function as drop-in replacement for easybuild provided ones, you may do the following: - pretend you actually want to build the EB provided-ones - dive inside the provided builds and rewire the subdirectories with symlinks If your previous modules really function well as drop-in replacement, this should work. Caveat: this has a manual procedure and it is not totally reproducible. :-( > • The generated module files set some classic env vars (e.g. > $LD_LIBRARY_PATH) and some EasyBuild specific ones (e.g. $EBROOTGOMPI). Our > current module system also sets some other env vars (e.g. PRACE_CFLAGS). > What would be the easiest way to instruct EasyBuild to set these extra env > vars? As said, this is kinda tracked via this issue: https://github.com/hpcugent/easybuild-easyblocks/issues/82 Indeed, a great majority of PRACE modules is already there, in fact, there exist easyconfigs already for goolf (gnu) and ictce (intel) toolchains. What you ask about is adding `modextravars` in file PRACE-ENV-20130605.eb from here: https://github.com/fgeorgatos/easybuild.experimental/tree/master/users/fgeorgatos/PRACE Also, file PrgEnv-gnu-20130605-goolf-1.4.10.eb, would make the top-level module available. How else you may help this business: - Test the above modextravars solution over *existing* PRACE build processes - Ask PRACE fellows to clarify page: http://www.prace-ri.eu/PRACE-Common-Production - Update the current PRACE easyconfigs & deps (toolchains & bash come to mind) - Read about $CC & pushenv in section V->G of the paper presented today at SC’14: "Modern Scientific Software Management Using EasyBuild and Lmod" This requires some extra work, yet the foundation is pretty much there. - test, test, test... Also, if I was you and may be using Lmod, I’d rather have PRACE-ENV as a "sticky" module, since that is the intention of the spec, to my understanding. enjoy, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
