diff options
| author | Owen Solberg <odoublewen@users.noreply.github.com> | 2019-05-18 19:00:32 -0700 |
|---|---|---|
| committer | Adam J. Stewart <ajstewart426@gmail.com> | 2019-05-18 21:00:32 -0500 |
| commit | 92604ed5760cbde70d0d705b5fab0a2682b1eb66 (patch) | |
| tree | e8ee3b6efb628e1e2689c2b0e6149b6d47fd9cb9 /bin | |
| parent | e592262da87282491ca58f060b246fb63c8391cc (diff) | |
| download | spack-92604ed5760cbde70d0d705b5fab0a2682b1eb66.tar.gz spack-92604ed5760cbde70d0d705b5fab0a2682b1eb66.tar.bz2 spack-92604ed5760cbde70d0d705b5fab0a2682b1eb66.tar.xz spack-92604ed5760cbde70d0d705b5fab0a2682b1eb66.zip | |
intel-tbb: fix patch for old compilers (#11371)
* added patch for intel-tbb@2019.1: with old compilers
* sparately specify when @:2018 and @2019
the reason we can't say @:2019 is that would include @2019.1 where the
patch doesn't work.
* should be possible to list when constraint as @:2019
According to my reading of ["Version ranges" in the Spack
docs](https://spack.readthedocs.io/en/latest/packaging_guide.html#version-ranges),
this should apply to up to `2019` but not `2019.1:`
* @:2019.0 appears to be necessary to specify 2019 but not 2019.1
* specifying 2019.1 2019.2 2019.3 2019.4 separately and explcitly
* flake8 fixes for long lines.
* add comments to explain why so many different patch directives
* remove blank like for flake8
* revert spec %gcc@4.8.0:4.99999 -> %gcc@4.8.0:
Diffstat (limited to 'bin')
0 files changed, 0 insertions, 0 deletions