Hi Franky, Thanks for sharing the debug bootstrap log after we discussed this last week.
More below... On 27 Jan 2014, at 14:52, Jens Timmerman wrote: > > On 01/27/2014 11:34 AM, Backeljauw Franky wrote: >> Hello all, >> >> Im trying to install Easybuild-1.10 on Scientific Linux 5.4 which has 2.4.3 >> installed. This fails with the message “MODULEPATH not set”. It does not >> help if I set this path explicitly via “export MODULEPATH=…”. >> >> I have attached the output, and hope that you can help me with the >> installation… >> >> — Regards, >> >> Franky Backeljauw >> >> >> > Franky, > > What version of environment-modules do you have installed? > I think this is fixed in a more recent environment-modules version [0] > > And we do recommend you use >=3.2.10, since some bad bugs were fixed in > this version. [1] > > > Regards > Jens Timmerman > > [0] http://sourceforge.net/p/modules/bugs/38/ > [1] https://github.com/hpcugent/easybuild/wiki/Dependencies The debug bootstrap log was really helpful. It shows that $MODULEPATH *is* set, right before "module purge" is executed: == 2014-01-23 16:18:58,287 bootstrap_eb.EnvironmentModulesC DEBUG Current MODULEPATH: /tmp/easybuild-VulHQ3/tmp8jykMB/all:/user/antwerpen/200/vsc20001/ebtest/modules/all:/user/antwerpen/200/vsc20001/ebtest/modules ... == 2014-01-23 16:18:58,287 bootstrap_eb.EnvironmentModulesC DEBUG Running module command '/usr/bin/modulecmd python purge ' from /tmp/tmpCzQhMb/EasyBuild/1.10.0/dummy-dummy/easybuild-framework-1.10.0 ... == 2014-01-23 16:18:58,295 bootstrap_eb.EnvironmentModulesC ERROR EasyBuild crashed with an error (at easybuild/tools/build_log.py:69 in caller_info): ModuleCmd_Purge.c(112):ERROR:107: 'MODULEPATH' not set So, to be more specific: the problem is that "module purge" is failing because no modules are loaded. It's complaining about $MODULEPATH not being set, but the real problem is that $LOADEDMODULES isn't set, i.e. no modules are loaded when running "module purge". This is fixed in environment modules v3.2.8 and up, as discussed in [0] mentioned by Jens. I follow Jens in recommending you to update to v3.2.10, also because an important bug was fixed in that version w.r.t. a modulecmd segfault that only occurs with "large" module environments (e.g. the ones easily obtained with EasyBuild). That being said, EasyBuild can help here as well, i.e. we can make sure we only run "module purge" when module are actually loaded; there's no using in running it when no modules are loaded. I'll look into that, after I figure out a way to check whether modules are loaded or not that works with the different module tools that EB currently supports (C env mods, Tcl env mods, Lmod, ...). regards, Kenneth
