Redirecting Jed's question specifically for PETSc configure. Can we/should we save the modules setting at configure time and then check them always at make time? Is some environmental variable set that has a unique value based on the modules loaded? If this is a common problem for us then we should be doing this. Barry

Begin forwarded message:

From: Jed Brown <[email protected]> To: Barry Smith <[email protected]>, "Bartlett, Roscoe A." <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [ideas-xsdk] common configure/cmake arguments for XSDK packages ready for testing Date: December 22, 2014 at 1:08:39 PM CST

Barry Smith <[email protected]> writes:

...

It is the issue of secretly mistakenly set values that is the reason for the environmental flag

Also, can we detect when the user has changed their "module" settings? A sizable fraction of support messages come from people using a different environment to build than they used to configure. Cray uses CC=cc in all cases, but "cc" has different behavior based on which modules are used. Moreover, the Intel compiler behaves differently based on which "gcc" is found in PATH. These changes invalidate configure tests.