[ET Trac] [Einstein Toolkit] #1668: Cannot compile the ET on Datura

[Einstein Toolkit]

#1668: Cannot compile the ET on Datura
-----------------------+----------------------------------------------------
  Reporter:  hinder    |       Owner:                     
      Type:  defect    |      Status:  new                
  Priority:  critical  |   Milestone:                     
 Component:  Other     |     Version:  development version
Resolution:            |    Keywords:                     
-----------------------+----------------------------------------------------

Comment (by hinder):

 I think you are referring to the fact that since you need to load modules
 to use bluewaters, you are forced to have one machine definition per
 compiler, in order to use multiple envsetup variables?  I think having a
 "machine" for each compiler (or other optional things, such as mpi
 version) is the right way to solve this.  At the moment, this requires a
 lot of duplicated text in the machine definition files.  This could be
 solved by allowing machine definitions to inherit from other machines.  So
 bluewaters-cray.ini would just be
 {{{
 [bluewaters-cray]
 inherit-from = bluewaters
 envsetup        = source /etc/profile && module unload PrgEnv-cray PrgEnv-
 gnu PrgEnv-intel PrgEnv-pathscale PrgEnv-pgi && module load PrgEnv-cray &&
 module load atp && module swap cce cce/8.1.5 && module load fftw/3.3.0.1
 && module load hdf5/1.8.8 && module load papi/5.0.1
 }}}
 Wanting to "mix and match" different options for a given machine and give
 them a name seems like quite a useful thing to be able to do in general.
 The name "machine" might be a little confusing if the concept is extended
 to mean a combination of machines and choices of the options to use on
 those machines.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1668#comment:2>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit