On Mon, Aug 5, 2013 at 2:43 PM, Kenneth Hoste <[email protected]> wrote: > On 12 Jul 2013, at 17:41, Ward Poelmans wrote: >> Futher I have a small suggestion for the FAQ on github: if you have >> cuda in your CPATH, C_INCLUDE_PATH or LIBRARY_PATH, you can get weird >> gcc building errors. So, I think it's a good idea to unset those >> variables prior to building gcc if you get any strange error. > > Is there any reason why we shouldn't unset $CPATH, etc. in the GCC easyblock, > prior to building GCC? > > That's what an easyblock is for: implement all that is required to make a > build work, and then forget about it. > Better that than document it in some obscure corner of the web (e.g., the > EasyBuild FAQ), and hope that Google leads you to it if you run into the > problem. > > @Ward: Are you up to creating a PR for this? I would unset $CPATH etc. during > the GCC build, but make sure the original values are restored after the GCC > build (just in case they're required for other builds in the same run). > > Maybe we should even make this a generic feature, i.e. implement it in the > framework somewhere, and simply supply a list of variable names that should > be unset during a build. $DISPLAY is a another example of this pattern, and > I'm sure there are others...
I've created an issue (#673) to make this a generic feature. It's not hard to do this but I'm not quite sure where to put it? tools/environment.py? https://github.com/hpcugent/easybuild-framework/issues/673 Ward
