Hi Joachim, On 12-04-17 16:13, Joachim Hein wrote: > > Sorry, if that is a silly question, but I couldn’t see this documented. > I have a user who likes to use the system EasyBuild to build packages in > their private space using the modules we provided. If in user mode, I > load the EB module and initiate an install using the system eb config > and adding --installpath=$HOME/eb_test to the build statement. The > build will not use the toolchains (e.g. foss/2016b) already systemwide > installed, but will rebuild it in $HOME/eb_test. > > Obviously if I don’t add an installpath, it will fail since I don’t > allow users to write the centrailised location. > > Is using the systemwide module and extending this privately supported in EB?
Yes, it is. I do it all the time. You need to set the MODULEPATH to point to the system locations and the user modules. Easybuild also needs access to the easyconfigs for all the installed modules (they need to be in the robot path). If that is all done, `eb --installpath=$HOME/eb_test` should pick up the system toolchains. If not, please share the output when run with --debug. Ward
