| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
* gptune: new test API
* gptune: cleanup; finish API changes; separate unrelated test parts
* gptune: standalone test cleanup with timeout constraints
* gptune: ensure stand-alone test bash failures terminate; enable in CI
* gptune: add directory to terminate_bash_failures
* gptune/stand-alone tests: use satisifes for checking variants
---------
Co-authored-by: Tamara Dahlgren <dahlgren1@llnl.gov>
|
|
* makedepf90: new package
* reorder versions and dependencies
|
|
* Add numactl 2.0.16-2.0.18
* Create link-with-latomic-if-needed-v2.0.16.patch
Add a link to libatomic, if needed, for numactl v2.0.16.
* Add some missing patches to v2.0.16
* Create numactl-2.0.18-syscall-NR-ppc64.patch
In short, we need numactl to set __NR_set_mempolicy_home_node on ppc64, if it's not already defined.
* Apply a necessary patch for v2.0.18 on PPC64
* Add libatomic patch for v2.0.16
|
|
* py-poxy: add new package
* py-poxy: depends on misk >= 0.8.1
|
|
setup_dependent_…" (#46283)
This reverts commit 6f08db463149efdea126abf8fdc770f684b4199d.
|
|
|
|
`spack reindex` relies on projections from configuration to locate
installed specs and prefixes. This is problematic because config can
change over time, and we have reasons to do so when turning compilers
into depedencies (removing `{compiler.name}-{compiler.version}` from
projections)
This commit makes reindex recursively search for .spack/ metadirs.
|
|
|
|
|
|
Signed-off-by: Teague Sterling <teaguesterling@gmail.com>
|
|
Fix a regression in {variants.X} and {variants.X.value} spec format strings.
|
|
|
|
|
|
|
|
Should have been a link depenedency, not a build dependency.
|
|
and remove compiler conditionals [as amrex conflict with clang no longer exists since #22967]
|
|
* Add missing variant, already used in recipe (avxtiles)
* Add memopt variant
Co-authored-by: viveshar <vivek.sharma2@amd.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* py-httpcore: Added new version
* [py-httpcore]
- added version 0.18.0
- restructured dependencies as everything has a when and
type/when ordering was all over the place
* [py-httpcore] ordered dependencies in the order listed in v1.0.5 pyproject.toml
---------
Co-authored-by: Alex C Leute <aclrc@rit.edu>
|
|
|
|
* [py-torch-fidelity] New package
* [py-torch-fidelity] add patch to fix missing requirements.txt
|
|
(#44327)
When a package is running `setup_dependent_package` on a parent, ensure
that module variables like `spack_cc` are available. This was often
true prior to this commit, but externals were an exception.
---------
Co-authored-by: John Parent <john.parent@kitware.com>
|
|
|
|
* Updated version of sz3
Supercedes #46128
* Add Robertu94 to maintainers fo r SZ3
---------
Co-authored-by: Robert Underwood <runderwood@anl.gov>
|
|
* New package: py-monai
* Fixed linked issues with py-monai
* [py-monai] removed extra line
* [py-monai]
- New version 1.3.2
- ran black
- update copyright
* [py-monai] added license
* [py-monai]
- moved build only dependencies
- specified newer python requirements for newer versions
---------
Co-authored-by: vehrc <vehrc@rit.edu>
|
|
These options have been deprecated in v0.21, and
slated for removal in v0.23
|
|
* Add libfabric v1.22.0 and v1.21.1
* Fix whitespace
|
|
|
|
Supercedes #46128
Co-authored-by: Robert Underwood <runderwood@anl.gov>
|
|
* Add exaca 2.0
* Add kokkos/cuda/hip backend support for exaca
|
|
* Replace if ... in spec with spec.satisfies in f* and g* packages
* gromacs: ^amdfftw -> ^[virtuals=fftw-api] amdfftw
* flamemaster: add virtuals lapack for the amdlibflame dependency
---------
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
|
|
|
|
|
|
cupy 12 needs a newer version of cudnn as documented here. Supercedes #46128
Co-authored-by: Robert Underwood <runderwood@anl.gov>
|
|
superceds #46128
Co-authored-by: Robert Underwood <runderwood@anl.gov>
|
|
Allow flags from different sources (compilers, `require:`, command-line
specs, and `depends_on`) to be merged together, and enforce a consistent
order among them.
The order is based on the sources, e.g. flags on specs from the command
line always come last. Some flag order consistency issues are fixed:
1. Flags from `compilers.yaml` and the command line were always intra- and
inter-source order consistent.
2. Flags from dependents and packages.yaml (introduced via `require:`)
were not: for `-a -b` from one source and `-c` from another, the final
result might rearrange `-a -b`, and would also be inconsistent in terms
of whether `-c` came before or after.
(1) is/was handled by going back to the original source, i.e., flags are
retrieved directly from the command line spec rather than the solver.
(2) is addressed by:
* Keeping track of grouped flags in the solver
* Keeping track of flag sources in the solver on a per-flag basis
The latter info is used in this PR to enforce DAG ordering on flags
applied from multiple dependents to the same package, e.g., for this
graph:
```
a
/|\
b | c
\|/
d
```
If `a`, `b`, and `c` impose flags on `d`, the combined flags on `d` will
contain the flags of `a`, `b`, and `c` -- in that order.
Conflicting flags are allowed (e.g. -O2 and -O3). `Spec.satisifes()` has
been updated such that X satisfies Y as long as X has *at least* all of
the flags that Y has. This is also true in the solver constraints.
`.satisfies` does not account for how order can change behavior (so
`-O2 -O3` can satisfy `-O3 -O2`); it is expected that this can be
addressed later (e.g. by prohibiting flag conflicts).
`Spec.constrain` and `.intersects` have been updated to be consistent
with this new definition of `.satisfies`.
|
|
|
|
|
|
Spack can now bootstrap two new dependencies on Windows: GnuPG, and file.
These dependencies are modeled as a separate package, and they install a cross-compiled binary.
Details on how they binaries are built are in https://github.com/spack/windows-bootstrap-resources
|
|
|
