Hi Kenneth, Thanks. I am actually using an older release of modules (from our default/base installation):
Modules Release 3.2.9 2011-11-24 (Copyright GNU GPL v2 1991): Todd From: Kenneth Hoste <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> List-Post: [email protected] Date: Monday, February 10, 2014 at 11:14 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [easybuild] module unload for toolchains? Hi Todd, On 10/02/14 16:56, Heywood, Todd wrote: Hi Pablo, I only just got to this now. I tried your change (line 157 of module_generator.py), and I also tried this: "if { ![is-loaded %(mod_name)s] } {", " module load %(mod_name)s", “} else {", " module unload %(mod_name)s", “} "", I regenerated modulefiles via eb. Unfortunately, the first try had no effect for unloading, and the second resulted in not being able to unload or purge any modules. I’m probably missing something fundamental. I'm currently looking into fleshing out Pablo's PR a bit more to add a configure option for the wrapping of module names in the is-loaded conditional, which triggers 'recursive unloading'. Are you saying that wrapping the module name in single quotes as shown below does not trigger recursive unloading at your end? if { ![is-loaded %(mod_name)s]} { # NO recursive unloading vs if { ![is-loaded '%(mod_name)s']} { # WITH recursive unloading Which modules tool are you using (environment modules, Lmod, ...), and which version? Also: I agree with your amazement that simply wrapping the module name in single quotes (note: double quotes don't work >_<) has such a 'major' effect... Has anyone been able to find a reference for that? Is this documented somewhere? regards, Kenneth
