| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* cflags and cxxflags from packages.yaml need to be passed into QMCPACK's CMake explictly for now.
* You need the ifcore library from the Intel compler to be manually linked in when you linked against a LAPACK provider that is not MKL.
|
|
tarball posted 2019-04-15
https://www.open-mpi.org/software/ompi/v3.0/
dantopa@cn209:openmpi-3.0.4-5ienfvwpcxky3nz5jt3rygxzxzltkwm4 $ cd lib/
dantopa@cn209:lib $ ls -alh
total 27M
...
lrwxrwxrwx 1 dantopa dantopa 16 Apr 17 10:01 libmpi.so -> libmpi.so.40.0.5
confirmation builds Darwin (LANL):
x86_64
-- linux-centos7-x86_64 / gcc@4.8.5 -----------------------------
5ienfvw openmpi@3.0.4%gcc
bkkhvej ^hwloc@1.11.11%gcc
5chyfxo ^libpciaccess@0.13.5%gcc
bcnjbc3 ^libxml2@2.9.8%gcc
tt2hkol ^numactl@2.0.12%gcc
64vg6e4 ^zlib@1.2.11%gcc
ARM
-- linux-rhel7-aarch64 / gcc@4.8.5 ------------------------------
cq2y6b3 openmpi@3.0.4%gcc
7gqvelc ^hwloc@1.11.11%gcc
6a4he35 ^libpciaccess@0.13.5%gcc
6a5uzd6 ^libxml2@2.9.8%gcc
m5neuus ^numactl@2.0.12%gcc
67s2oqn ^zlib@1.2.11%gcc
Power9
-- linux-rhel7-ppc64le / gcc@4.8.5 ------------------------------
otirvfn openmpi@3.0.4%gcc
r6cylpu ^hwloc@1.11.11%gcc
uzm3xdv ^libpciaccess@0.13.5%gcc
trik6hj ^libxml2@2.9.8%gcc
pmgndwh ^numactl@2.0.12%gcc
4v3ticy ^zlib@1.2.11%gcc
2019-04-18
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
|
|
* Make a separate CDash report for each package installed
Previously, we generated a single CDash report ("build") for the complete results
of running a `spack install` command. Now we create a separate CDash build for
each package that was installed.
This commit also changes some of the tests related to CDash reporting.
Now only one of the tests exercises the code path of uploading to a
(nonexistent) CDash server. The rest of the related tests write their reports
to disk without trying to upload them.
* Don't report errors to CDash for successful packages
Convert errors detected by our log scraper into warnings when the package
being installed reports that it was successful.
* Report a maximum of 50 errors/warnings to CDash
This is in line with what CTest does. The idea is that if you have more than
50 errors/warnings you probably aren't going to read through them all anyway.
This change reduces the amount of data that we need to transfer and store.
|
|
|
|
pumi
slepc
plasma
magma
trilinos
alquimia
pflotran
strumpack
tasmanian
amrex
hypre
omega-h
superlu-dist
|
|
|
|
* Update spec format to simpler syntax, maintain backwards compatibility
* Switch to new spec.format method throughout internals
* update package files for new format strings
* documentation and minor code cleanup. removed nonsensical variant sigils
|
|
* Initial commit for v2.0 of the CEED software suite.
* Update Nek packages and gslib
* Help spack concretize the hypre version for ceed-2.0.
* Fix nekcem install error
* Add support for gfortran v8 in nek5000 and nekcem.
* Split Nek5000 into Nek5000 and Nektools
* Get Nektools to build fine in Theta
* Fix travis failure: remove unused 'import numbers' from nek5000.
* Check for gfortran if it is wrapped
* Tweak the detection of gfortran in nek5000.
* Fix Nek packages to add -std=legacy when FC=gcc
* spack install ceed~petsc works fine on Theta
* Fix flake8 errors
* Fix more flake8 tests
* Fix an import issue
* Tweak the suite-sparse package to avoid interaction with existing system
installations of suite-sparse.
* petsc: update superlu-dist dependency
* Updates in the packages: occa, libceed, and ceed.
* In the libceed package, explicitly tell nvcc which host compiler to use.
* Fix python formatting.
* Simplify the test for gfortran in nek* packages.
* ceed: 2.0 uses petsc@3.11.0
* hpgmg-0.4; use from ceed@2.0.0
* Update the hypre dependency for ceed 2.0.
* Disable the superlu-dist dependency (through hypre) when using a
+quickbuild of ceed 2.0.
* petsc-3.11.0: add xlf fix
* nekcem: has a build dependency on Python 2.7+
* hpgmg: better setting of compiler options and use python for configure
* libceed: use v0.4 tag
* libceed: fix 0.4 release oops (pkgconfig version)
* Add a patch for magma-2.5.0 that brings it up the current 'master'.
* In the mfem package, install the examples, miniapps, and data under
$prefix/share/mfem.
* In the magma package, apply a patch to v2.5.0 that disables
magma_sparse - for testing purposes.
* In the magma package, link the 'magma' library with the
'nvToolsExt' library.
* In the magma package, update the 'magma-2.5.0.patch' with the latest
commits from the magma source repository. Also, remove the library
'nvToolsExt' from the 'magma-2.5.0-cmake.patch' - now it is not
needed.
* In the magma package, disable OpenMP when using v2.5.0 with the
IBM XL compiler.
Please enter the commit message for your changes. Lines starting
* In the mfem package, add version for the 'laghos-v2.0' tag; also,
prefix the versions `laghos-v*` with their respective development
version numbers -- this way they are properly ordered within spack
relative to the official numbered versions.
* petsc: add version 3.11.1 (#11179)
(cherry picked from commit 1eab6e3c865836d209db4621d0cd44bc8663656b)
* ceed-2.0: use petsc-3.11.1
* this-is-so-dumb.f -> empty.f
|
|
* mpifileutils v0.9.1
* mpifileutils v0.9.1 for realz
|
|
- Add 3.2.1
- Reformat versions to include proper upstream version tags
- Add gtk dependency
- Add prefix to PATH so sublime_text can be found
|
|
Fixes #11070 #11010
Spack attempts to intercede on behalf of all compiler invocations for
a build. This involves adding its wrappers to PATH. Cray systems
include a "ftn" executable and Spack was only redirecting this call
when the Spec was built with cce. This updates the compiler wrappers
to add "ftn" in all cases.
|
|
If specifying ~openssl, the post-install step will still try to install
the non-existent certificate, leading to an IOError.
|
|
|
|
Ref: https://github.com/spack/spack/issues/11202
|
|
|
|
|
|
|
|
|
|
The default (implied) behavior for all environments, as of ea1de6b,
is that an environment will maintain a view in a location of its
choosing. ea1de6b explicitly recorded all three possible states of
maintaining a view:
1. Maintain a view, and let the environment decide where to put it
(default)
2. Maintain a view, and let the user decide
3. Don't maintain a view
This commit updates the config writer so that for case [1], nothing
will be written to the config.yaml. This will not change any existing
behavior, it just serves to keep the config more compact.
|
|
|
|
* Added openmpi 3.1.4
* fix suffix comment
|
|
|
|
* Add versions 1.4.0, 1.3.0, and 1.2.0
* Add dependencies and update constraints (e.g. version 1.4.0 of
precice requires a later version of boost)
* Add maintainers
|
|
Still look for BASH_SOURCE[0] first, but if it's not set,
_sp_source_file is initialized to an empty value addressing the
unset parameter error (line 217).
|
|
A Spack hack for MKL usage was needed in QMCPACK prior to version 3.5
when non-Intel compilers were used. This Spack hack could have
undesirable side-effects and led to ugly code that was extra work to
maintain. For older versions of QMCPACK, we throw a conflict if you
want to use Intel MKL with the other compilers commonly found on x86.
Note that there is no impact to version of QMCPACK since 3.5.
|
|
explicitly specified (#11187)
Version 6 added dependency on LAPACK - so additional -DTPL_LAPACK_LIBRARIES option is required
Ref: https://github.com/xiaoyeli/superlu_dist/issues/36
Ref: https://github.com/spack/spack/issues/10173
|
|
|
|
Compilers are treated separately from other dependencies in Spack.
#10761 added the option to automatically install compilers when a
package specifies using a compiler that is not available in Spack.
However, this did not work correctly for dependency packages (it
would only build a compiler for the root of an install DAG). This
commit enables the building of compilers for dependency packages.
|
|
|
|
|
|
|
|
|
|
Similar to #10956 flex needs to be a link-dependency for verilator in
order for FlexLexer.h to be found during install.
|
|
Also added maintainers
|
|
* Limit to FASTMath-only packages
* Replace boxlib with amrex
As requested by @asalmgren
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit edits the Makefile to use github.com mirrors rather than the
default mirrors of the dependency packages installed by GO.
|
|
|
|
Environments are nowm by default, created with views. When activated, if an environment includes a view, this view will be added to `PATH`, `CPATH`, and other shell variables to expose the Spack environment in the user's shell.
Example:
```
spack env create e1 #by default this will maintain a view in the directory Spack maintains for the env
spack env create e1 --with-view=/abs/path/to/anywhere
spack env create e1 --without-view
```
The `spack.yaml` manifest file now looks like this:
```
spack:
specs:
- python
view: true #or false, or a string
```
These commands can be used to control the view configuration for the active environment, without hand-editing the `spack.yaml` file:
```
spack env view enable
spack env view envable /abs/path/to/anywhere
spack env view disable
```
Views are automatically updated when specs are installed to an environment. A view only maintains one copy of any package. An environment may refer to a package multiple times, in particular if it appears as a dependency. This PR establishes a prioritization for which environment specs are added to views: a spec has higher priority if it was concretized first. This does not necessarily exactly match the order in which specs were added, for example, given `X->Z` and `Y->Z'`:
```
spack env activate e1
spack add X
spack install Y # immediately concretizes and installs Y and Z'
spack install # concretizes X and Z
```
In this case `Z'` will be favored over `Z`.
Specs in the environment must be concrete and installed to be added to the view, so there is another minor ordering effect: by default the view maintained for the environment ignores file conflicts between packages. If packages are not installed in order, and there are file conflicts, then the version chosen depends on the order.
Both ordering issues are avoided if `spack install`/`spack add` and `spack install <spec>` are not mixed.
|
|
|
|
|
|
Add documentation for the Spack chain feature added in #8772
|
|
* Fix bug when system perl is used.
If system perl is being used through packages.yaml there cannot be dependent modules.
The setup_dependent_packages function should not do anything in that case.
|
