summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-04-17Features: Improve Spec format strings (#10556)Greg Becker42-180/+568
* Update spec format to simpler syntax, maintain backwards compatibility * Switch to new spec.format method throughout internals * update package files for new format strings * documentation and minor code cleanup. removed nonsensical variant sigils
2019-04-17[WIP] CEED 2.0 (#10903)Veselin Dobrev18-144/+926
* Initial commit for v2.0 of the CEED software suite. * Update Nek packages and gslib * Help spack concretize the hypre version for ceed-2.0. * Fix nekcem install error * Add support for gfortran v8 in nek5000 and nekcem. * Split Nek5000 into Nek5000 and Nektools * Get Nektools to build fine in Theta * Fix travis failure: remove unused 'import numbers' from nek5000. * Check for gfortran if it is wrapped * Tweak the detection of gfortran in nek5000. * Fix Nek packages to add -std=legacy when FC=gcc * spack install ceed~petsc works fine on Theta * Fix flake8 errors * Fix more flake8 tests * Fix an import issue * Tweak the suite-sparse package to avoid interaction with existing system installations of suite-sparse. * petsc: update superlu-dist dependency * Updates in the packages: occa, libceed, and ceed. * In the libceed package, explicitly tell nvcc which host compiler to use. * Fix python formatting. * Simplify the test for gfortran in nek* packages. * ceed: 2.0 uses petsc@3.11.0 * hpgmg-0.4; use from ceed@2.0.0 * Update the hypre dependency for ceed 2.0. * Disable the superlu-dist dependency (through hypre) when using a +quickbuild of ceed 2.0. * petsc-3.11.0: add xlf fix * nekcem: has a build dependency on Python 2.7+ * hpgmg: better setting of compiler options and use python for configure * libceed: use v0.4 tag * libceed: fix 0.4 release oops (pkgconfig version) * Add a patch for magma-2.5.0 that brings it up the current 'master'. * In the mfem package, install the examples, miniapps, and data under $prefix/share/mfem. * In the magma package, apply a patch to v2.5.0 that disables magma_sparse - for testing purposes. * In the magma package, link the 'magma' library with the 'nvToolsExt' library. * In the magma package, update the 'magma-2.5.0.patch' with the latest commits from the magma source repository. Also, remove the library 'nvToolsExt' from the 'magma-2.5.0-cmake.patch' - now it is not needed. * In the magma package, disable OpenMP when using v2.5.0 with the IBM XL compiler. Please enter the commit message for your changes. Lines starting * In the mfem package, add version for the 'laghos-v2.0' tag; also, prefix the versions `laghos-v*` with their respective development version numbers -- this way they are properly ordered within spack relative to the official numbered versions. * petsc: add version 3.11.1 (#11179) (cherry picked from commit 1eab6e3c865836d209db4621d0cd44bc8663656b) * ceed-2.0: use petsc-3.11.1 * this-is-so-dumb.f -> empty.f
2019-04-17mpifileutils v0.9.1 (#11216)Elsa Gonsiorowski, PhD1-0/+1
* mpifileutils v0.9.1 * mpifileutils v0.9.1 for realz
2019-04-17sublime-text: Miscellaneous improvements (#11154)Michael Kuhn1-4/+10
- Add 3.2.1 - Reformat versions to include proper upstream version tags - Add gtk dependency - Add prefix to PATH so sublime_text can be found
2019-04-17Add ftn to lib/spack/env (#11180)Satish Balay1-0/+1
Fixes #11070 #11010 Spack attempts to intercede on behalf of all compiler invocations for a build. This involves adding its wrappers to PATH. Cray systems include a "ftn" executable and Spack was only redirecting this call when the Spec was built with cce. This updates the compiler wrappers to add "ftn" in all cases.
2019-04-17ruby: Install certificate for +openssl only (#11184)Oliver Breitwieser1-10/+11
If specifying ~openssl, the post-install step will still try to install the non-existent certificate, leading to an IOError.
2019-04-17gromacs: added 2019 patch releases (#11211)Christoph Junghans1-0/+2
2019-04-17strumpack@3.1.1: add patch for Intel-19 build failure on cori (#11204)Satish Balay2-0/+48
Ref: https://github.com/spack/spack/issues/11202
2019-04-17astral: add 5.6.1 (#11195)Justin S1-0/+2
2019-04-17Add llvm 8.0.0 (#11197)sknigh1-0/+16
2019-04-17lz4: Add 1.9.0 (#11207)Michael Kuhn1-0/+1
2019-04-17zstd: Add 1.4.0 (#11208)Michael Kuhn1-0/+1
2019-04-16don't record 'view: True' in environment config (#11182)Peter Scheibel1-1/+8
The default (implied) behavior for all environments, as of ea1de6b, is that an environment will maintain a view in a location of its choosing. ea1de6b explicitly recorded all three possible states of maintaining a view: 1. Maintain a view, and let the environment decide where to put it (default) 2. Maintain a view, and let the user decide 3. Don't maintain a view This commit updates the config writer so that for case [1], nothing will be written to the config.yaml. This will not change any existing behavior, it just serves to keep the config more compact.
2019-04-16Added rust 1.34.0 (#11200)sknigh1-0/+1
2019-04-16Added openmpi 3.1.4 (#11201)sknigh1-1/+2
* Added openmpi 3.1.4 * fix suffix comment
2019-04-16New package: CLN library (#11167)Matthias Mayr1-0/+31
2019-04-16precice package: add versions and dependencies (#11176)Frédéric Simonis1-3/+10
* Add versions 1.4.0, 1.3.0, and 1.2.0 * Add dependencies and update constraints (e.g. version 1.4.0 of precice requires a later version of boost) * Add maintainers
2019-04-16setup-env.sh: fix zsh compatibility error (#11153)paulanda1-3/+3
Still look for BASH_SOURCE[0] first, but if it's not set, _sp_source_file is initialized to an empty value addressing the unset parameter error (line 217).
2019-04-16QMCPACK package: Remove Spack MKL hack for older version (#11127)Nichols A. Romero1-18/+23
A Spack hack for MKL usage was needed in QMCPACK prior to version 3.5 when non-Intel compilers were used. This Spack hack could have undesirable side-effects and led to ugly code that was extra work to maintain. For older versions of QMCPACK, we throw a conflict if you want to use Intel MKL with the other compilers commonly found on x86. Note that there is no impact to version of QMCPACK since 3.5.
2019-04-16superlu-dist: fix issue with adding system blas/lapack - when MKL is ↵Satish Balay1-2/+2
explicitly specified (#11187) Version 6 added dependency on LAPACK - so additional -DTPL_LAPACK_LIBRARIES option is required Ref: https://github.com/xiaoyeli/superlu_dist/issues/36 Ref: https://github.com/spack/spack/issues/10173
2019-04-16Add unit tests for Cray compiler detection (#11191)Adam J. Stewart1-0/+11
2019-04-15Bugfix: Install missing compilers for dependency packages (#11175)Greg Becker1-9/+8
Compilers are treated separately from other dependencies in Spack. #10761 added the option to automatically install compilers when a package specifies using a compiler that is not available in Spack. However, this did not work correctly for dependency packages (it would only build a compiler for the root of an install DAG). This commit enables the building of compilers for dependency packages.
2019-04-15add charliecloud 0.9.9 (#11190)Jordan Ogas1-0/+1
2019-04-15cmake: add version 3.14.2 (#11192)Matthias Diener1-0/+1
2019-04-15pixman: fix patch (#11173)Denis Davydov1-1/+1
2019-04-15boost: add 1.70.0 (#11183)Denis Davydov1-2/+4
2019-04-15verilator: Fix FlexLexer.h not found (#11185)Oliver Breitwieser1-1/+1
Similar to #10956 flex needs to be a link-dependency for verilator in order for FlexLexer.h to be found during install.
2019-04-15petsc4py: add verson 3.11.0 (#11186)Satish Balay1-0/+4
Also added maintainers
2019-04-12Update FASTMath metapackage (#11171)Mark C. Miller1-3/+1
* Limit to FASTMath-only packages * Replace boxlib with amrex As requested by @asalmgren
2019-04-12petsc: add fftw variant (#11178)Satish Balay1-1/+4
2019-04-12petsc: add version 3.11.1 (#11179)Satish Balay1-0/+1
2019-04-12py-deeptools: adding release 3.2.1 sha256 sum (#11174)Owen Solberg1-0/+1
2019-04-11Updated Sphinx configuration (#11165)Massimiliano Culpo3-4/+13
2019-04-11intel: optionally take gcc executable from cflags (#11136)Denis Davydov1-3/+15
2019-04-11xsdk@develop: enable amrex@develop+sundials (#11169)Satish Balay1-2/+2
2019-04-11amrex: add sundials variant (#11147)Cody Balos1-1/+5
2019-04-10libxsmm package: add variant to build generator executables (#11114)brietzke1-0/+10
2019-04-10fzf package: change mirror and add vim plugin (#10920)clellsolomon2-3/+39
This commit edits the Makefile to use github.com mirrors rather than the default mirrors of the dependency packages installed by GO.
2019-04-10New Packages: ecp-io-sdk and ecp-viz-sdk (#11073)Chuck Atkins2-0/+91
2019-04-10Maintain a view for an environment (#10017)Peter Scheibel7-114/+569
Environments are nowm by default, created with views. When activated, if an environment includes a view, this view will be added to `PATH`, `CPATH`, and other shell variables to expose the Spack environment in the user's shell. Example: ``` spack env create e1 #by default this will maintain a view in the directory Spack maintains for the env spack env create e1 --with-view=/abs/path/to/anywhere spack env create e1 --without-view ``` The `spack.yaml` manifest file now looks like this: ``` spack: specs: - python view: true #or false, or a string ``` These commands can be used to control the view configuration for the active environment, without hand-editing the `spack.yaml` file: ``` spack env view enable spack env view envable /abs/path/to/anywhere spack env view disable ``` Views are automatically updated when specs are installed to an environment. A view only maintains one copy of any package. An environment may refer to a package multiple times, in particular if it appears as a dependency. This PR establishes a prioritization for which environment specs are added to views: a spec has higher priority if it was concretized first. This does not necessarily exactly match the order in which specs were added, for example, given `X->Z` and `Y->Z'`: ``` spack env activate e1 spack add X spack install Y # immediately concretizes and installs Y and Z' spack install # concretizes X and Z ``` In this case `Z'` will be favored over `Z`. Specs in the environment must be concrete and installed to be added to the view, so there is another minor ordering effect: by default the view maintained for the environment ignores file conflicts between packages. If packages are not installed in order, and there are file conflicts, then the version chosen depends on the order. Both ordering issues are avoided if `spack install`/`spack add` and `spack install <spec>` are not mixed.
2019-04-10py-requests: Add missing dependencies for versions 2.16.0 and up (#10996)Eric Martin1-0/+5
2019-04-10Unload altd and darshan (#11162)Mario Melara1-1/+1
2019-04-10Add documentation for chaining Spack instances (#11152)Peter Scheibel3-0/+102
Add documentation for the Spack chain feature added in #8772
2019-04-10Fix bug when system perl is used. (#11034)Patrick Gartung1-7/+11
* Fix bug when system perl is used. If system perl is being used through packages.yaml there cannot be dependent modules. The setup_dependent_packages function should not do anything in that case.
2019-04-10dealii: fix build with tbb from intel parallel studio (#11138)Denis Davydov1-1/+13
2019-04-10suite-sparse: fix tbb patching (#11155)Denis Davydov1-1/+1
2019-04-09libfabric: Add 1.7.1 (#11141)Michael Kuhn1-0/+1
2019-04-09wget: add version 1.20.3 (#11148)Matthias Diener1-0/+1
2019-04-09Typo: Unkown -> Unknown (#11150)George Hartzell1-1/+1
2019-04-09intel: consolidate libs() in the base class (#11143)Denis Davydov3-31/+10
* intel: consolidate libs() in the base class * white space * flake8