- May 14, 2019
-
-
Justin S authored
-
Jon Rood authored
The --enable-relax-coord-bound option was added in 1.8.0. NetCDF 4.6.3 enabled relax coords by default and required it from PNetCDF. PNetCDF 1.10.0 enabled it by default but for versions between 1.8.0 and 1.10.0 it should be enabled explicitly.
-
Peter Scheibel authored
CUDA 10.0 provides Compatability libraries for running newer versions of CUDA with older drivers. These do not work with newer drivers.
-
Justin S authored
* megadock: new package at 4.0.3 * megadock: remove CudaPackage redundancies * megadock: move env vars to build targets, use cuda_arch variant * megadock: flake8 fixes, more flexible mathlib
-
Jon Rood authored
* Fix py-yt for Python 2 by requesting older py-ipython version. * Add conflicts statement to py-ipython because version 7: is not compatible with python@2.7
-
william-dawson authored
-
Greg Becker authored
Remove a vestigial print statement introduced in #8570
-
- May 13, 2019
-
-
Jon Rood authored
-
Justin S authored
-
Levi Baber authored
* rename py-pauvr to py-pauvre
-
George Zagaris authored
f242f5f8 removed spec.architecture.platform_os, which was used to test an option in the 'm4' package. The attribute is now accessed as 'spec.architecture.os'.
-
Adam J. Stewart authored
-
- May 11, 2019
-
-
Todd Gamblin authored
-
Todd Gamblin authored
-
- May 10, 2019
-
-
Todd Gamblin authored
- Trying to get our Python 2.6 tests working again. - This seems to crash travis in the 2.6 environment, for whatever reason.
-
Todd Gamblin authored
-
Shane R. Spencer authored
-
Chuck Atkins authored
-
Hans Pabst authored
-
Jon Rood authored
-
Chris Green authored
* Add versions 3.27.{0,1,2} and 3.28.0 * Add url_for_version: the URL format includes the year so this function maps version ranges to years * Restore patches for versions removed in 84c547cf: this commit removed versions before 3.26.0 due to a security issue with FTS support. Add a +fts variant (default true) that enables FTS support along with a conflict for +fts with earlier versions.
-
Todd Gamblin authored
- Codecov cannot handle as many coverage reports as we are generating - as a result, our PR coverage pages have been broken for a while, and it's hard to tell people where to enhance their testing in PR reviews. - Scale back to only running coverage for 3.7 and 2.7 unit tests - This is *probably* better. We run the build tests for good measure, but we do not need to evaluate them for coverage. The coverage reports are about unit tests.
-
Chuck Atkins authored
-
xfzhao authored
* py-pauvr:new package * py-pauvr: using url and Releases * py-pauvr: remove extra comments
-
Greg Becker authored
* Don't overwrite suid/sgid bits when setting permissions * add tests for permission setting
-
Glenn Johnson authored
Add fixes to support multiple installs and dependents using a subset of IntelPackage functionality. * Update IntelPackage to only return scalapack libraries if the root spec depends on MPI: scalapack requires MPI to be mentioned as a dependency in the DAG. Package builds using intel-mkl for its blas/lapack implementations but not for scalapack were failing to build. Ideally it would be possible to ask if any of the packages in the DAG are actually requesting the scalapack functionality provided by the IntelPackage and only return scalapack libs in that case, but that is not easily done at this time. Fixes #11314 Fixes #11289 * set HOME when the intel silent installer is run. This prevents the installer from using the ~/intel directory (which can cause conflicts for multiple installs of the same IntelPackage) Fixes #9713
-
- May 09, 2019
-
-
Greg Becker authored
Use new `module` function instead of `get_module_cmd` Previously, Spack relied on either examining the bash `module()` function or using the `which` command to find the underlying executable for modules. More complicated module systems do not allow for the sort of simple analysis we were doing (see #6451). Spack now uses the `module` function directly and copies environment changes from the resulting subprocess back into Spack. This should provide a future-proof implementation for changes to the logic underlying the module system on various HPC systems.
-
Peter Josef Scheibel authored
The license text is now expected to match almost exactly (not accounting for formatting in different file types (e.g. rst vs. bash script vs. python)
-
Peter Josef Scheibel authored
-
Peter Josef Scheibel authored
-
Mark W. Krentel authored
* Starting with the upcoming 10.1 release, Dyninst changed the names of some cmake args to camel case: LIBELF_* to LibElf_* and LIBDWARF_* to LibDwarf_*. This change is needed now for @develop and will be used for 10.1 when it is released. * New versions of Dyninst now requires cmake version 3.4.0 or later. * Restrict boost dependency version to < 1.70.0 to avoid build error
-
David Gardner authored
-
Tiziano Müller authored
... and apply this in SIRIUS, CP2K & QE. Thanks to @scheibelp for the idea.
-
Tiziano Müller authored
-
Tiziano Müller authored
-
Tiziano Müller authored
-
Tiziano Müller authored
-
Tiziano Müller authored
-
Tiziano Müller authored
-
Jerome Soumagne authored
Use tarballs instead of git tags Fix openpa dependency on gcc < 4.9 Fix boost dependency Change sm variant default to true
-