summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2020-12-17docs: add single node concurrent build example (#20416)Tamara Dahlgren1-4/+11
2020-12-17OpenCV: add versions up to v4.5.0, variants (#20378)Adam J. Stewart1-29/+27
2020-12-17flexi: new package (#20313)Michael Kuhn1-0/+41
2020-12-17openblas: added v0.3.13 (#20357)Michael Kuhn1-0/+6
2020-12-17mbedtls: added v2.16.9 (#20422)Ryan Mast1-0/+1
2020-12-17DBoW2: add new package (#20387)Adam J. Stewart1-0/+21
2020-12-17acts: added v3.00.0 (#20402)Hadrien G1-0/+1
2020-12-17arm: added new package (#18019)Massimiliano Culpo1-0/+86
The package is at the moment not installable, just detectable.
2020-12-17xlc, xlf: added new packages (#18154)Massimiliano Culpo2-0/+150
2020-12-17unit-tests: ensure that installed packages can be reused (#20307)Massimiliano Culpo1-0/+84
refers #20292 Added a unit test that ensures we can reuse installed packages even if in the repository variants have been removed or added.
2020-12-17help2man: update to 1.47.16 (#20397)Ryan Mast1-0/+1
2020-12-16sundials: add versions up to 5.6.1 (#20436)Ryan Mast1-0/+2
2020-12-16Added PyAMG package. (#20414)Ben Cowan1-0/+25
2020-12-16cli11: add new package (#20398)Ryan Mast1-0/+26
2020-12-16PythonPackage: add import module smoke tests (#20023)Adam J. Stewart241-1046/+335
2020-12-16ninja: update to version 1.10.2 (#20399)Ryan Mast1-0/+1
2020-12-16AMD ROCm release for mivisionx Bump up versions - 3.9.0 and 3.10.0 (#20401)arjun-raj-kuppala1-2/+4
2020-12-16dlib: add new package (#20386)Adam J. Stewart1-0/+21
2020-12-16pylikwid: New recipe (#20408)Thomas Gruber1-0/+31
2020-12-16automake: update to 1.16.3 (#20421)Ryan Mast1-0/+1
2020-12-16Update the plumed 2.6.2 (#20425)Zhiyi Wu1-1/+2
2020-12-16docs: fix spack install debug arg order (#20428)Greg Becker1-4/+3
2020-12-16Version update to 5.3.0 (#20433)Desmond Orton1-0/+2
2020-12-16Add RAJA v0.13.0 (#20431)David Beckingsale1-0/+1
2020-12-16Docs: add more Command Reference links to spack test (#20413)Adam J. Stewart1-2/+12
2020-12-16Match master version instead of develop for PARAVIEW_VTK_DIR (#20427)Ethan Stam1-1/+1
2020-12-16docs: fix spack command for unit-test pytest help (#20415)Tamara Dahlgren1-1/+1
2020-12-16loop fuser option (#20417)Danny Taller1-2/+4
2020-12-16Added TFEL v3.4 and MGIS v1.2 (#20234)thelfer2-3/+13
2020-12-15Fix comparisons for abstract specs (#20341)Greg Becker2-3/+29
bug only relevant for python3
2020-12-15Kluge to get the gfortran linker to work correctly for SciPy on Big Sur. ↵Ben Cowan1-0/+8
(#20367) * Kluge to get the gfortran linker to work correctly on Big Sur. * Fixed formatting error; stetting the other. * Removed spaces. * Added comment, mainly to re-trigger Spack CI.
2020-12-15concretizer: don't use one_of_iff for range constraints (#20383)Todd Gamblin2-58/+50
Currently, version range constraints, compiler version range constraints, and target range constraints are implemented by generating ground rules from `asp.py`, via `one_of_iff()`. The rules look like this: ``` version_satisfies("python", "2.6:") :- 1 { version("python", "2.4"); ... } 1. 1 { version("python", "2.4"); ... } 1. :- version_satisfies("python", "2.6:"). ``` So, `version_satisfies(Package, Constraint)` is true if and only if the package is assigned a version that satisfies the constraint. We precompute the set of known versions that satisfy the constraint, and generate the rule in `SpackSolverSetup`. We shouldn't need to generate already-ground rules for this. Rather, we should leave it to the grounder to do the grounding, and generate facts so that the constraint semantics can be defined in `concretize.lp`. We can replace rules like the ones above with facts like this: ``` version_satisfies("python", "2.6:", "2.4") ``` And ground them in `concretize.lp` with rules like this: ``` 1 { version(Package, Version) : version_satisfies(Package, Constraint, Version) } 1 :- version_satisfies(Package, Constraint). version_satisfies(Package, Constraint) :- version(Package, Version), version_satisfies(Package, Constraint, Version). ``` The top rule is the same as before. It makes conditional dependencies and other places where version constraints are used work properly. Note that we do not need the cardinality constraint for the second rule -- we already have rules saying there can be only one version assigned to a package, so we can just infer from `version/2` `version_satisfies/3`. This form is also safe for grounding -- If we used the original form we'd have unsafe variables like `Constraint` and `Package` -- the original form only really worked when specified as ground to begin with. - [x] use facts instead of generating rules for package version constraints - [x] use facts instead of generating rules for compiler version constraints - [x] use facts instead of generating rules for target range constraints - [x] remove `one_of_iff()` and `iff()` as they're no longer needed
2020-12-15fmt: added v7.1.3, update URLs (#20404)Dr. Christian Tacke1-2/+3
2020-12-15bison: added versions up to v3.7.4 (#20400)Ryan Mast1-0/+5
2020-12-15gromacs: removed mentions of non-existing variants (#20405)AMD Toolchain Support1-1/+0
2020-12-15dealii, piranha, trilinos: remove mentions of non-existing variants (#20406)Massimiliano Culpo3-6/+2
2020-12-15Bugfix/docs: correct and expand smoke test documentation (#20278)Tamara Dahlgren1-70/+151
2020-12-15comgr: disable hip compile test from /opt/rocm (#20330)Mark W. Krentel2-2/+20
2020-12-15outputs: restore default output of fetch/build/total times (#20394)Tamara Dahlgren1-5/+4
2020-12-15package sanity: ensure all variant defaults are allowed values (#20373)Massimiliano Culpo19-25/+36
2020-12-14Bugfix: Correct the git URL (#20391)Tamara Dahlgren1-1/+1
2020-12-14ParaView: add new ParaView-5.9.0-RC2 release (#20222)Vicente Bolea1-2/+3
* ParaView: add new ParaView-5.9.0-RC2 release Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com> * Update var/spack/repos/builtin/packages/paraview/package.py Indeed, I misunderstood the previous review. This looks good to me too. Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-12-14bazel: add latest versions up to 3.7.1 (#20355)Ryan Mast1-1/+4
2020-12-14boost: added v1.75.0 (#20366)Tim Haines1-0/+1
2020-12-14mysql: fixed variant mismatch with boost (#20370)Andre Sailer1-1/+1
Require boost at cxxstd=14 if cxxstd=14 is selected, not 11
2020-12-14likwid: Add variant for Nvidia GPU profiling feature (#20337)Thomas Gruber1-4/+34
2020-12-14WarpX: PSATD on (#20342)Axel Huebl1-4/+4
Enabling PSATD is not mutually exclusive with other runtime options anymore, so we can always compile with support for it to ease usability.
2020-12-14Propagate cuda_arch downstream from LBANN, Hydrogen and DiHydrogen (#20345)Brian Van Essen3-2/+12
2020-12-14gradle: updated versions up to v6.7.1 (#20358)Ryan Mast1-1/+38
2020-12-14concretizer: remove clingo command-line driver (#20362)Todd Gamblin1-216/+0
I was keeping the old `clingo` driver code around in case we had to run using the command line tool instad of through the Python interface. So far, the command line is faster than running through Python, but I'm working on fixing that. I found that if I do this: ```python control = clingo.Control() control.load("concretize.lp") control.load("hdf5.lp") # code from spack solve --show asp hdf5 control.load("display.lp") control.ground([("base", [])]) control.solve(...) ``` It's just as fast as the command line tool. So we can always generate the code and load it manually if we need to -- we don't need two drivers for clingo. Given that the python interface is also the only way to get unsat cores, I think we pretty much have to use it. So, I'm removing the old command line driver and other unused code. We can dig it up again from the history if it is needed.