summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2019-04-24squashfs should depend_on('zlib') (#11265)George Hartzell1-0/+1
Add zlib dependency to squashfs On my CentOS system it was getting linked in (from Spack, no less) fortuitously. On a minimal Ubuntu system it failed until it was added as an explicit dependency.
2019-04-24_valid_tokens list is missing intended comma (#11271)Daryl W. Grunau1-1/+1
* _valid_tokens list is missing a needed comma
2019-04-23ftgl: update to 2.1.3-rc5. (#11214)Chris Green2-15/+161
* ftgl: update to 2.1.3-rc5. This updates to the last release (from 2008) with patches required to work with Spack and Root. * Working 2.1.2 with/without docs, 2.1.3-rc5 without.
2019-04-23py-umi-tools: Add latest versions (#11256)Eric Martin1-0/+3
2019-04-22Install squashfs exe's into prefix.bin, not prefix (#11246)George Hartzell1-1/+1
The squashfs Makefile's `INSTALL_DIR` args is the path to the `bin` directory, not the top of the install tree. Adjust accordingly.
2019-04-23Update tutorial page with RIKEN tutorial slides. (#11254)Todd Gamblin1-13/+28
- Add link to container image, as well as a description of VMs - Update slide link to point to latest RIKEN tutorial
2019-04-22Fix transitions between tutorial sections (#11251)Greg Becker3-11/+21
2019-04-20spack edit: use execv instead of Executable (#11245)Todd Gamblin3-37/+262
- `spack edit` previously used `spack.util.executable` `Executable` objects, and didn't `exec` the editor like you'd expect it to - This meant that Spack was still running while your editor was, and stdout/stdin were being set up in weird ways - e.g. on macOS, if you call `spack edit` with `EDITOR` set to the builtin `emacs` command, then type `Ctrl-g`, the whole thing dies with a `==> Error: Keyboard interrupt` - Fix all this by changing spack.util.editor to use `os.execv` instead of Spack's `Executable` object
2019-04-20OpenBLAS: Allow enabling/disabling AVX2/512 supportJanne Blomqvist1-1/+18
Allow specifying whether AVX2 or AVX512 should be enabled or disabled on x86 targets. As AVX2 hardware and toolchain support is quite ubiquitous by now, AVX2 is enabled by default. Also AVX2 support is not disabled when building the +virtual_machine variant. AVX512 is not supported in older but still supported toolchains, hardware is still expensive, and OpenBLAS AVX512 kernels still have bugs. Thus AVX512 is disabled by default.
2019-04-20Fix detection of LLVM-enabled PGI compilers (#10704)Adam J. Stewart2-2/+12
* Fix detection of LLVM-enabled PGI compilers * Add unit tests for LLVM-enabled PGI compiler version detection
2019-04-20hdf5: add symbols (#10991)Matthias Diener1-0/+1
2019-04-20Mercury package: add version 1.0.1 and update dependencies (#10906)Adam J. Stewart3-32/+136
* Add Mercury version 1.0.1 * Remove cci and bmi dependency requirements: these are not currently defined in Spack. If +bmi is enabled, the effect is that it may use a system install of bmi * Add a note that fabtests is deprecated and has been folded into the libfabric package. Add the fabtests resource to the libfabric package * Add CMake option settings to Mercury based on variant settings * Mercury: Set OFI testing protocol depending on how libfabric was built * Mercury: add version constraints to dependencies
2019-04-20Move NoLibrariesError/NoHeadersError into error.py (#10997)Denis Davydov3-11/+20
Also add constructor to NoLibrariesError which can either take an error message (like other SpackErrors) or a name and prefix (in which case the error message is constructed).
2019-04-20dealii: add patch for build with boost@1.70.0 (#11239)Satish Balay1-0/+5
Ref: https://github.com/dealii/dealii/issues/7934
2019-04-19miniconda 2 and 3 packages: add version 4.6.14 (#11232)Sajid Ali2-2/+4
2019-04-19Fix outdated R packages failing to fetch (#11039)Justin S1-3/+4
PR #10758 made a slight change to find_versions_of_archive() which included archive_url in the search process. While this fixed `spack create` and `spack checksum` missing command-line arguments, it caused `spack install` to prefer those URLs over those it found in the scrape process. As a result, the package url was treated as a list_url causing all R packages to stop fetching once the package was updated on CRAN. This patch is more selective about including the archive_url in the remote versions, explicitly overriding it with matching versions found by the scraper.
2019-04-19mysql: 5.7.X versions link boost (#11237)Chris Green1-4/+4
Fixes #11226 MySQL 5.7.X and Boost 1.59.0 have a closer relationship than MySQL >= 8.0 and their corresponding Boost versions: 5.7.X needs to link against boost libraries which is indicated by marking boost as a link dependency (removing the 'type' reverts to the default, which includes link and build).
2019-04-19jdk package: Fix fetching with curl 7.64.0+ (#11108)Oliver Breitwieser1-2/+2
Starting with version 7.64.0, curl skips cookies specified with "-H" (generic custom header specification) when following redirects, which causes the "accept-license"-cookie for jdk to disappear. The result is that jdk fails to download. This uses the "-b" option (which is used specifically for configuring cookies) instead, which is more permissive.
2019-04-19MUMPS: add version 5.2.0 (#11234)Satish Balay1-0/+1
2019-04-19hypre: add @osborn9 to maintainers (#11233)Satish Balay1-1/+1
2019-04-19Fix backwards compatibility for module naming (#11236)Greg Becker1-0/+4
f242f5f8 changed the format strings but maintained backwards compatibility in all cases except one: The list of valid tokens for the module naming schemes was not updated properly to contain both the new and old styles for compilers and package names. This PR re-adds the old tokens into the list of valid tokens.
2019-04-19added libsodium 1.0.16 and 1.0.17 (#11231)kustowski11-0/+2
2019-04-19petsc: fix suitesparse configure options. (#11188)Satish Balay1-1/+1
spec['dep'].libs.ld_flags can return system paths in some cases. This is a targeted fix for the petsc package when retrieving suite-sparse dependency libraries.
2019-04-19hpx: overhaul of the package recipe (#11194)Massimiliano Culpo1-6/+111
* added latest versions + malloc variant * added a variant to activate different instrumentations * added a variant to activate or not networking * added a variant to activate or not cuda and tools * enforce c++ standard and make it consistent with boost
2019-04-18memsurfer: add new packageHarsh Bhatia1-0/+48
2019-04-18vtk: add version 8.1.2Harsh Bhatia1-0/+1
2019-04-18cgal: add version 4.13Harsh Bhatia1-0/+1
2019-04-18Spack chain docs: config should go in upstreams.yaml (#11225)Peter Scheibel1-14/+12
#11152 added documentation for #8772 but some details were based on an earlier implementation that had changed by the time #8772 was merged. In particular, #11152 mentioned that upstream Spack instances were configured in config.yaml, when in fact they should be placed in a separate upstreams.yaml config file; this PR updates the documentation accordingly.
2019-04-18Moved cleanup before raising (the code couldn't be reached before)Massimiliano Culpo1-3/+3
2019-04-18Cleaned get methods of Repo and RepoPathMassimiliano Culpo1-5/+3
2019-04-18Used functools.wrap for the decorator + reordered importsMassimiliano Culpo1-20/+23
2019-04-18Removed 'namespace' argument from Repo and RepoPathMassimiliano Culpo1-32/+19
fixes #11159 The 'namespace' argument to both Repo and RepoPath were used to set the "super namespace". Currently it seems to be vestigial as the only "super namespace" allowed for packages is 'spack.pkg' since 39c9bbf
2019-04-18QMCPACK CMake fix (#11212)Nichols A. Romero1-0/+20
* 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.
2019-04-18Add Open MPI v3.0.4 (#11221)Daniel Topa1-0/+1
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>
2019-04-18improvements to our CDash reporter (#11168)Zack Galbreath2-84/+127
* 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.
2019-04-18Prevent building llvm@8: with an incompatilble gcc (#11220)Federico Ficarelli1-1/+2
2019-04-18xsdk: add/update maintainers to xsdk packages (#11146)Satish Balay14-4/+25
pumi slepc plasma magma trilinos alquimia pflotran strumpack tasmanian amrex hypre omega-h superlu-dist
2019-04-18new package: kitty terminal (#9621)Stephen Herbein7-1/+74
2019-04-17Features: Improve Spec format strings (#10556)Greg Becker42-180/+568
* 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
2019-04-17[WIP] CEED 2.0 (#10903)Veselin Dobrev18-144/+926
* 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
2019-04-17mpifileutils v0.9.1 (#11216)Elsa Gonsiorowski, PhD1-0/+1
* mpifileutils v0.9.1 * mpifileutils v0.9.1 for realz
2019-04-17sublime-text: Miscellaneous improvements (#11154)Michael Kuhn1-4/+10
- 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
2019-04-17Add ftn to lib/spack/env (#11180)Satish Balay1-0/+1
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.
2019-04-17ruby: Install certificate for +openssl only (#11184)Oliver Breitwieser1-10/+11
If specifying ~openssl, the post-install step will still try to install the non-existent certificate, leading to an IOError.
2019-04-17gromacs: added 2019 patch releases (#11211)Christoph Junghans1-0/+2
2019-04-17strumpack@3.1.1: add patch for Intel-19 build failure on cori (#11204)Satish Balay2-0/+48
Ref: https://github.com/spack/spack/issues/11202
2019-04-17astral: add 5.6.1 (#11195)Justin S1-0/+2
2019-04-17Add llvm 8.0.0 (#11197)sknigh1-0/+16
2019-04-17lz4: Add 1.9.0 (#11207)Michael Kuhn1-0/+1
2019-04-17zstd: Add 1.4.0 (#11208)Michael Kuhn1-0/+1