| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The 2.3 version of HPL needs LDFLAGS set for use of MKL libraries.
|
|
This fixes a few typos, adds a hint to `spack config blame` and brings
the variant specification in line with other docs sections.
|
|
Add the latest 2.3.0 release and me as package maintainer.
|
|
* new package: mutationpp
* Update package.py
* flake8: correct package.py for flake8-python-style
* Update package.py
* modifications as requested by reviewer for #11705
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* add charliecloud-0.9.10; remove obsolete version
* revert older version changes; add version function
* fix space issue
* remove url declaration
* revert url removal
* remove self reference
* fix url; removed preferred tag; use newer package url
|
|
The "spack location" command was previously untested. This also adds
a check to ensure that composite Stages can report whether they were
expanded (this property was previously only recorded in Stage but not
in CompositeStage).
|
|
DIYStage, used to treat a user-managed directory as a staging area,
should always be considered expanded (i.e. the source has been
decompressed if it was stored in an archive).
This also:
* Adds checks to ensure that the path used to instantiate a
DIYStage refers to an existing directory.
* Adds tests to check the behavior of DIYStage (including behavior
added here, but it was generally untested before).
|
|
Change 'destination' to 'placement' in the use of resource() for
intel-xed and hpcviewer. Recent commits (1842873f and eb584d89)
changed the directory path for a resource and thus broke the build
for these packages.
|
|
|
|
#11528 updated Stage to always store a Package's source in a fixed
directory accessible via `Stage.source_path` This left behind a
number of packages which were expecting to access the source code
via `Stage.path`. This Updates those packages to use
`Stage.source_path` instead.
This also updates the name of the fixed directory: The original name
of the fixed directory was "src", so if an expanded archive created a
"src" directory, then users inspecting the directory structure could
see paths like "src/src" (which wasn't wrong but could be confusing).
Therefore this also updates the name of the fixed directory to
"spack-src".
|
|
Fixes #11678
`spack compiler find` was not searching `PATH` when provided with no
arguments. ea7910a updated the API for the search function and the
command logic did not update how it called this function. This also
adds a test to ensure that `spack compiler find` will collect
compilers from `PATH`.
|
|
* warpx: only allow master branch, and fix build on darwin
* warpx: Added CXXFLAGS=-std=c++11 for clang
* warpx: further clean up of openmp and c++11 flags
* warpx: Get around the problem with resources
The update uses placement instead of destination
|
|
Fixed logic behind flecsi backends to not require legion for an mpi
build and to better support required combinations.
Also made graphviz support and tutorial building optional
|
|
* Add additional common C++ and Fortran header file extensions
* Add .hxx extension
* Add .txx and .tcc extensions
* Add .icc extension
|
|
* new python package/py-typesentry
* add proper version
|
|
* Add support for python3 in new versions of VTK.
|
|
|
|
* Paraview/VTK: Fix failure on intel builds
Paraview@5.6.0 fails to build with intel compilers on certain platforms.
Error messages have been traced to the optional MotionFX lib.
(see https://discourse.paraview.org/t/error-build-5-6-0-rc1/572)
Turning off motionfx allows for succesful builds on these platforms.
|
|
"spack module tcl find -r <spec>" (and equivalents for other module
systems) was failing when a dependency was installed in an upstream
Spack instance. This updates the module index to handle locating
module files for upstream Spack installations (encapsulating the
logic in a new class called UpstreamModuleIndex); the updated index
handles the case where a Spack installation has multiple upstream
instances.
Note that if a module is not available locally but we are using the
local package, then we shouldn't use a module (i.e. if the package is
also installed upstream, and there is a module file for it, Spack
should not use that module). Likewise, if we are instance X using
upstreams Y and Z like X->Y->Z, and if we are using a package from
instance Y, then we should only use a module from instance Y. This
commit includes tests to check that this is handled properly.
|
|
* Add latest releases for pFUnit
- 3.2.10, 3.3.0, 3.3.1, 3.3.2, 3.3.3
- 3.2.9 now with sha256
- 4.0.0 is added, but commented out (build fails, see errors)
Verification builds
Darwin x86_64:
dantopa@cn100:pr-pfunit-darwin-general.spack $ spack find pfunit
==> 5 installed packages
-- linux-centos7-x86_64 / gcc@4.8.5 -----------------------------
pfunit@3.2.9 pfunit@3.2.10 pfunit@3.3.0 pfunit@3.3.1 pfunit@3.3.2 pfunit@3.3.3
Darwin Power9:
-- linux-rhel7-ppc64le / gcc@4.8.5 ------------------------------
pfunit@3.2.9 pfunit@3.2.10 pfunit@3.3.0 pfunit@3.3.1 pfunit@3.3.2 pfunit@3.3.3
Darwin ARM:
dantopa@cn805:pr-pfunit-darwin-arm.spack $ spack find pfunit
==> 5 installed packages
-- linux-rhel7-aarch64 / gcc@4.8.5 ------------------------------
pfunit@3.2.9 pfunit@3.2.10 pfunit@3.3.0 pfunit@3.3.1 pfunit@3.3.2 pfunit@3.3.3
2019-05-05
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
* answer @citibeth comments
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
* shortened offending comment to comply with flake8; suppressed error message on entry for v4.0.0
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
* removed tailing space qt 20:55
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
|
|
|
|
Use python3 for latest paraview and catalyst versions.
|
|
Build the docker image for the new package index REST API on each
merge/push to develop and master.
|
|
|
|
|
|
* Adding the dateutils package
* Removing superfluous dependencies
|
|
- also remove coverage calls of these commands
- we JUST want coverage to tell us what is in the test suite.
|
|
(#11594)
Spack currently tries to unify everything in the DAG, but this is too strict for build dependencies, where it is fine to build a dependency with a tool that conflicts with a version fo that tool for a dependent's build.
To enable a workaround for conflicts among build dependencies, so that users can install in multiple steps to avoid these conflicts, make the following changes:
* Dont apply package dependency constraints for build deps of installed packages
* Avoid applying constraints for installed packages vs. concrete packages
* Mark all dependencies of installed packages as visited in normalization method
* don't remove dependency links for concrete specs in flat_dependencies
Also add tests:
* Update test to ensure that link dependencies of installed packages have constraints applied
* Add test to check for proper handling of transitive dependencies (which is currently not the case)
|
|
* fix qt build on gcc8.3
* source patches from upstream
* remove old code adding the same patch
|
|
ADIOS2 is the latest implementation of the ADaptable Input Output System,
ADIOS. This brand new architecture was designed to continue supporting the
performance legacy of ADIOS, and extend its current capabilities to address
current and future input/output (IO) challenges in the scientific data
lifecycle through effective research and development (R&D) activities.
ADIOS2 was recently added as a Third Party Library of Trilinos when it
was integrated to IOSS, a library inside the SEACAS package.
|
