In this particular instance, it seems that just unsetting LIBS *may* have worked. Thanks for the input!
> On 14/10/2015, at 7:46 PM, Kenneth Hoste <[email protected]> wrote: > > > > On 13/10/15 20:28, Ward Poelmans wrote: >> On Tue, Oct 13, 2015 at 7:57 PM, Ward Poelmans <[email protected]> >> wrote: >> >>> On Tue, Oct 13, 2015 at 6:58 PM, Kenneth Hoste <[email protected]> >>> wrote: >>> >>>> No, but you can do the reverse (as you already know, I think), using the >>>> 'unwanted_env_vars' easyconfig parameter, that takes a list of names of >>>> environment variables that should be unset. >>>> I think this is a better approach too: see what makes the build trip, and >>>> unset that. $LIBS is a common one. >>>> >>> That doesn't work. `unwanted_env_vars` only works for variables not set by >>> EB. >>> >> Addition, you can unset a variable using buildopts etc: >> buildopts = "unset LIBS && " >> will work. The hard part is of course finding which variable is causing >> havoc. >> > > I stand corrected, sorry for the confusion, thanks Ward! > > Just unsetting whatever is causing problems is probably better though... > > Through an easyblock, you can use the unset_env_vars function which is > available from easybuild.tools.environment. > > > regards, > > Kenneth
