| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* lock down packages that export targets to pre-BLT 0.4.0 so that they can move forward when ready
* don't default to 0.4.0
|
|
(#23354)
* simplify compiler flag logic and suppress warning that gets promoted to an error on certain files in gcc/clang
|
|
* Metall: add version 0.2
* Add Metall v0.3
* Update Metall package to v0.4 and v0.5.
* Metall package: add v0.6
* Metall package: add v0.7
* Metall package: add v0.8 and v0.9
* Add Metall package v0.10
* Metall package: set run_environment METALL_ROOT
* Metall package: removed blanks
* Metall package: add v0.11 and v0.12
* Metall package: change required cmake version
|
|
* qt: update versions and URLs
- Add LTS releases of 5.12.10, 5.9.9, 5.6.3
- Mark other minor versions of 5 as deprecated
- Use https
- The URL for older QT versions changed recently to "new_archive"
- Prefer xz instead of gz for >=5.6 because 5.6.3 isn't available as
gz. This invalidates the SHA of 5.7-5.8.
|
|
|
|
|
|
Co-authored-by: Sid Pendelberry <sid@rit.edu>
|
|
* mxnet: new version 1.8.0
use submodules on master
introduce constraints on cuda versions supported
handle USE_MKLDNN->USE_ONEDNN conversion
* * use define for USE_CUTENSOR
* fix up dependencies for 2.0.0+
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* py-luigi: add v3.0.1-3
* address review comments
* more review comments
|
|
|
|
|
|
|
|
|
|
The Relion package recipe had an extra "http://" in the url for the
homepage.
|
|
|
|
Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com>
|
|
libtirpc puts its header files under prefix/include/tirpc, but
spack was returning just prefix/include for location of headers.
This will cause spack to return both prefix/include and
prefix/include/tirpc for headers, so both
include <rpc/xdr.h>
or
include <tirpc/rpc/xdr.h>
should work.
|
|
Help dependents find libraries/headers. Like intel-oneapi-mkl, this
package offers several different versions of libraries that conflict.
This PR chooses one of those versions. When
https://github.com/spack/spack/discussions/22749 is resolved, this
package should be updated to choose which libraries to use.
|
|
|
|
|
|
|
|
|
|
Modified ncbi-rmblastn to retrieve patches from remote
|
|
* Added test for version intersections when one is prefix of another
* Fix version intersection for prefixes
|
|
A recently merged PR had a typo that slipped through CI. Here's a fix.
|
|
Co-authored-by: Scott McMillan <smcmillan@nvidia.com>
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Itaru Kitayama <itaru.kitayama@riken.jp>
|
|
Co-authored-by: Itaru Kitayama <itaru.kitayama@riken.jp>
|
|
|
|
|
|
|
|
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
|
|
* Add pic (for static) and debug variants
* explicitly add -g flag for +debug (even though it is in Makefile)
|
|
|
|
|
|
|
|
Previously the tau package got the cxx and cc names from
os.path.basename(self.compiler.cxx), however if the path to the compiler
looks like "/usr/bin/g++-10.2.0" then tau's custom build system doesn't
recognize it. What we want instead is something that looks like "g++"
which is exactly what cxx_names[0] gives us. We already did this for
fortran, so I am not sure why we didn't do it here. Not doing this
causes a build failure when tau tries to use a polyfill (vector.h,
iostream.h) that doesn't seem to be packaged with tau.
Additionally, tau needs some help finding mpi include directories when
building with MPI, so we provide them. Unfortunately, we can't just say
that the compilers are mpicc and mpicxx in the previous fix to have
these things found automatically. This is because tau assumes we always
need the polyfill when the compilers are set to these values which again
causes a build failure.
|
|
|
|
The function we coded in Spack to load Python modules with arbitrary
names from a file seem to have issues with local imports. For
loading hooks though it is unnecessary to use such functions, since
we don't care to bind a custom name to a module nor we have to load
it from an unknown location.
This PR thus modifies spack.hook in the following ways:
- Use __import__ instead of spack.util.imp.load_source (this
addresses #20005)
- Sync module docstring with all the hooks we have
- Avoid using memoization in a module function
- Marked with a leading underscore all the names that are supposed
to stay local
|
|
Complete overhaul of the Legion package to better capture a more
up-to-date set of configuration options and variants. This update
adds additional flexibility and features that were requested by
users.
* Add version 21.03.0 and "stable" branch
* Remove all older numeric versions
* Add support for CUDA, Python, PAPI support and more
* Add maintainer
* This no longer uses the Spack `gasnet` package: it defaults to
using an embedded gasnet or can be pointed to an external
|
