[petsc-dev] Fwd: [ideas-xsdk] common configure/cmake arguments for XSDK packages ready for testing

[Barry Smith]

  I couldn't find any environmental variables for softenv and haven't logged into a cray in decades. We don't have to abort for all changes but perhaps could produce warning text or detect serious changes?

  Barry

> On Dec 23, 2014, at 9:31 PM, Jed Brown <jed at jedbrown.org> wrote:
> 
> Barry Smith <bsmith at mcs.anl.gov> writes:
> 
>>  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?
> 
> We can do it for modules (like Cray) and softenv, but aborting in all
> cases of environment change is not tractable and would be too much
> noise.
> 
>>  If this is a common problem for us then we should be doing this.
> 
> It's a common problem in the sense that a lot of users get confused over
> this and it generates a significant amount of support email.