| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Add patch for proj@7 to support the new tiff interface shipped in cmake@3.19: This compliments the existing patch for @8 in #43780
|
|
|
|
#40773 introduced python-venv, which improved build isolation and avoids issues with,
e.g., `ubuntu`'s system python modifying `sysconfig` to include a (very unwanted)
`local` directory within the default install layout.
This addresses a few cases where #40773 removed functionality, without harming the
default cases where we use `python-venv`.
Traditionally, *every* view with `python` in it was essentially a virtual environment,
because we would copy the `python` interpreter and `os.py` into every view when linking.
We now rely on `python-venv` to do that, but only when it's used (i.e. new builds) and
only for packages that have an `extends("python")` directive.
This again makes every view with `python` in it a virtual environment, but only
if we're not already using a package like `python-venv`. This uses a different
mechanism from before -- instead of using the `virtualenv` trick of copying `python`
into the prefix, we instead create a `pyvenv.cfg` like `venv` (the more modern way
to do it).
This fixes two things:
1. If you already had an environment before Spack `v0.22` that worked, it would
stop working without a reconcretize and rebuild in `v0.22`, because we no longer
copy the python interpreter on link. Adding `pyvenv.cfg` fixes this in a more
modern way, so old views will keep working.
2. If you have an env that only includes python packages that use `depends_on("python")`
instead of `extends("python")`, those packages will now be importable as before,
though they won't have the same level of build isolation you'd get with `extends`
and `python-venv`.
* views: avoid making client code deal with link functions
Users of views and ViewDescriptors shouldn't have to deal with link functions -- they
should just say what type of linking they want.
- [x] views take a link_type, not a link function
- [x] views work out the link function from the link type
- [x] view descriptors and commands now just tell the view what they want.
* python: simplify logic for avoiding pyvenv.cfg in copy views
Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
|
|
* Add CMake 3.28.6
* Add 3.29.4
|
|
|
|
In #30882, we made Spack ignore `-Werror` calls so that it could more easily build
projects that inject `-Werror` into their builds. We did this by translating them to
`-Wno-error` in the compiler wrapper. However, some compilers (like `nvhpc`) do not
support `-Wno-error`. We need to exclude them from this feature until they do.
- [x] make a property on `PackageBase` for `keep_werror` that knows not to use it for
`nvhpc`.
- [x] update property so that it keeps only the specific `-Werror=...` args for newer nvhpc's,
which support `-Wno-error` but not `-Wno-error=...`
---------
Co-authored-by: William Mou <william.mou1024@gmail.com>
Co-authored-by: Tom Scogland <scogland1@llnl.gov>
Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
|
|
|
|
* duckdb: add v1.0.0, v0.10.3
* Adding issue reference
|
|
* Update nanobind dependency
* Update py-nanobind dependency
|
|
|
|
* Add nanobind 2.0.0
* Add dependency
* Fix dependency name
* Change "_" -> "-"
|
|
* Update py-vl-convert-python:
1. set version to 1.4.0
2. set version 1.3.0 deprecated since its rust dependency curve@4.1.1 is not able to compile
|
|
Co-authored-by: Owen Solberg <owen.solberg@sana.com>
|
|
* Add seqfu
---------
Co-authored-by: dialvarezs <dialvarezs@users.noreply.github.com>
|
|
(#44528)
|
|
When Spack concretizes environments, it prints every (newly concretized) root spec
individually with all of its dependencies. For most reasonably sized environments, this
is too much output. This is true for three commands:
* `spack concretize` when concretizing an environment with newly added specs
* `spack install` when installing an environment with newly added specs
* `spack spec` with no arguments in an environment
The output dates back to before we had unified environments or nicer spec traversal
routines, and we can improve it.
This PR makes environment concretization output analogous to what we do for regular
specs. Just like `spack spec` for a single spec, we show all root specs with no
indentation, so you can easily see the specs you explicitly requested. Dependencies are
shown:
1. With indentation according to their depth in a breadth-first traversal starting at
the roots;
2. Only once if they appear on paths from multiple roots
So, the default is now consistent with `spack spec` for one spec--it's `--cover=nodes`.
i.e., if there are 100 specs in your environment, you'll get 100 lines of output.
If you want to see more details, you can do that with `spack spec` using the arguments
you're already familiar with. For example, if you wanted to see dependency types and
*all* dependencies, you could use `spack spec -l --cover=edges`. Or you could add
deptypes and namespaces with, e.g. `spack spec -ltN`.
With no arguments in an environment, `spack spec` concretizes (if necessary) and shows
the concretized environment. If you run `spack concretize` *first*, inspecting the
environment repeatedly with `spack spec` will be fast, as everything is already in the
`spack.lock` file.
- [x] factor most logic of `Spec.tree()` out of `Spec` class into `spack.spec.tree()`,
which can take multiple specs as roots.
- [x] make `Spec.tree()` call `spack.spec.tree()`
- [x] `spack.environment.display_specs()` now uses `spack.spec.tree()`
- [x] Update `spack concretize`
- [x] Update `spack install`
- [x] Update `spack spec` to call `spack.spec.tree()` for environments.
- [x] Continue to output specs individually for `spack spec` when using
`--yaml` or `--json`
|
|
* new package: nb
* only one filter_file, install completions
* completions now implicit, merged by the view
|
|
|
|
|
|
* updating version for slate, blaspp, and lapackpp
* verified new hashes
|
|
* Protected against a known problem with mixed gcc/apple-clang toolchains. Fixes #44330
---------
Co-authored-by: Chrismarsh <Chrismarsh@users.noreply.github.com>
|
|
* Apply patch from upstream to allow vtk compilation with %gcc 12 and 14.
* Fixes #44331
* fix soec usage
* fix compiler version range
* Finalize version range, switch to .diff file
---------
Co-authored-by: Chrismarsh <Chrismarsh@users.noreply.github.com>
|
|
* Now need to explicitly depend on libfabric for Cray EX
* Ensure build uses the selected CUDA and ROCm versions
* Correct spelling on `configure --with-ldflags`
* Patch a defect regarding `configure --with-ldflags`
* Default to Spack's copy of GASNet-EX, which is newer than embedded
|
|
* Add GASNet v 2024.5.0
* cosmetic fix to info output
* Add a missing dependency
* Ensure GASNet detects the provided ROCm/CUDA dependency
* [@spackbot] updating style on behalf of bonachea
---------
Co-authored-by: bonachea <bonachea@users.noreply.github.com>
|
|
* Spglib: add version 2.4.0
* DLA-Future: fix +test option
* update
* [@spackbot] updating style on behalf of RMeli
* Apply suggestions from code review
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
---------
Co-authored-by: RMeli <RMeli@users.noreply.github.com>
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
|
|
* Adding gmsh 4.11.1
* Becoming a maintainer
---------
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
|
|
* update
* Apply suggestions from code review
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
---------
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
|
|
e2fsprogs: adding version 1.47.0 and fuse2fs variant
fuse-overlayfs: adding version 1.13
squashfuse: adding version 0.5.1 and 0.5.2
e2fsprogs: fixing audit errors
apptainer: expanding deps to cover more versions, fix binary_path logic.
apptainer: add go version deps, fix e2fsprogs patch sums, rework dep paths
fuse-overlayfs: tightening up the libfuse dep
Signed-off-by: Shane Nehring <snehring@iastate.edu>
|
|
|
|
* New package: password-store
* add bash completion as variant
* also patch the cygwin platform snippet
* update description and maintainers
* make completions implicit and don't overwrite the completions package
* remove completion option
* formatting
* clean up file filter syntax
* remove reference to completion variant
* remove dependency on bash-completion
* clarify comments
* bashcompdir is already the default
* add optional dependency on xclip
* fix formatting
|
|
Signed-off-by: Shane Nehring <snehring@iastate.edu>
|
|
* tamaas: install python extension with explicit pip call
* tamaas: patching compilation issues with recent compilers
* tamaas: added versions 2.7.0 and 2.7.1
|
|
Co-authored-by: rem1776 <rem1776@github.com>
|
|
* add dla-future@0.5.0
* [@spackbot] updating style on behalf of rasolca
* fix typo
* review suggestions
---------
Co-authored-by: rasolca <rasolca@users.noreply.github.com>
|
|
Co-authored-by: Simon Potter <sp39@sanger.ac.uk>
|
|
* util-macros: ensure url_for_version only used for older versions
* util-macros: use url.substitute_version after xz -> bz2
* util-macros: mv url_for_version down the file
|
|
* py-junit2html: new package, version '31.0.2'
* py-junit2html: install from sources instead of from wheel
|
|
LD_LIBRARY_PATH (#44171)
* Adding hsa library path in LD_LIBRARY_PATH
* Prepending instead of setting LD_LIBRARY_PATH to hsa-rocr-dev/lib
* adding rocm-opencl 6.1.0 & 6.1.1 updates
|
|
|
|
|
|
|
|
Using OMPI_ environment variables, like openmpi does.
|
|
Fixes a bug where custom keys to identify nodes were not passed
correctly.
|
|
|
|
|
|
|
|
* Spglib: add version 2.4.0
* DLA-Future: fix +test option
|
|
* refactor logic to switch to cmake for cuda management
|
|
|
|
`BuildcacheBootstrapper` uses `Spec.intersects` to match specs needed
for bootstrapping against the binary cache. The specs were not
sufficiently-detailed to prevent matching e.g. cached binaries for
Mac OS on Windows; this commit adds the platform to each requested
bootstrap spec to prevent that.
|
