diff options
author | Matt Belhorn <belhornmp@ornl.gov> | 2016-07-26 17:11:32 -0400 |
---|---|---|
committer | Matt Belhorn <belhornmp@ornl.gov> | 2016-07-27 11:37:15 -0400 |
commit | 3040381f03d962513d49406a6c45e12a952f3bc6 (patch) | |
tree | bc7a0be744674ab4d9a2401104244f8bde2bcc71 /LICENSE | |
parent | b1e6c58ff2de8ff5d729dd9a10e28bec41aebeeb (diff) | |
download | spack-3040381f03d962513d49406a6c45e12a952f3bc6.tar.gz spack-3040381f03d962513d49406a6c45e12a952f3bc6.tar.bz2 spack-3040381f03d962513d49406a6c45e12a952f3bc6.tar.xz spack-3040381f03d962513d49406a6c45e12a952f3bc6.zip |
Front-end unification for Cray systems.
A platform to generically cover all Cray systems is introduced to avoid having
specific platforms for each of XK (XE, XT), XC, and future systems using CrayPE
and CNL.
The platform searches for 'front_end' and 'back_end' targets, in order, from:
* Environment variables 'SPACK_FRONT_END' and 'SPACK_BACK_END'
* A spack configuration file 'targets.yaml'
* Parsing `/etc/bash.bashrc.local` for first loaded CrayPE CPU target.
If a back_end target is not found through one of these methods, an exception is
raised. Otherwise, the back_end is set as the default target. The shell init
script search is based on recommendations in Crayports case #144359.
No automagic way of determining front_end targets has been found (to date) so if
a front_end is not specified through configuration, it is ignored which should
leave a spack instance in a consistant state.
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions