summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2020-07-12Add new package: atf (#17472)darmac1-0/+23
2020-07-12Magics fix and update (#17477)Jannek Squar1-3/+16
* Added new versions to magics and began to set not-so-optional netcdf dependency * Added enforced netcdf dependency * Fix also works for version 4.1.0
2020-07-11update docs on point releases (#17463)Greg Becker1-41/+37
2020-07-11lmbench: fix scripts path for aarch64 (#17456)darmac2-0/+15
2020-07-11llvm-flang: Only build offload code if cuda enabled (#17466)Dr Owain Kenway1-3/+4
* llvm-flang Only build offload code if cuda enabled The current version executes `cmake(*args)` always as part of the post install. If device offload is not part of the build, this results in referencing `args` without it being set and the error: ``` ==> Error: UnboundLocalError: local variable 'args' referenced before assignment ``` Looking at prevoous version of `llvm-package.py` this whole routine appears to be only required for offload, some indent `cmake/make/install` to be under the `if`. * Update package.py Add comment
2020-07-10Merge branch 'releases/v0.15' into developPeter Josef Scheibel4-6/+26
2020-07-10[glew] depends on libsm and libice (#17428)Jen Herting1-0/+2
* [glew] depends on libsm * [glew] depends on libice
2020-07-10energyplus: add 9.3.0 (#17452)Justin S1-8/+11
* energyplus: add 9.3.0 * energyplus: fix version order * energyplus: more concise links * energyplus: avoid join_path
2020-07-10tensorflow-serving-client: add new version 2.2.0 (#17462)figroc1-1/+2
2020-07-10Bump version to 0.15.1; update CHANGELOG and version referencesv0.15.1Peter Josef Scheibel4-6/+26
2020-07-10spack install: improve error message with no args (#17454)Greg Becker2-2/+37
The error message was not updated when the behavior of Spack environments was changed to not automatically activate the local environment in #17258. The previous error message no longer makes sense.
2020-07-10installation: skip repository metadata for externals (#16954)Greg Becker1-3/+8
When Spack installs a package, it stores repository package.py files for it and all of its dependencies - any package with a Spack metadata directory in its installation prefix. It turns out this was too broad: this ends up including external packages installed by Spack (e.g. installed by another Spack instance). Currently Spack doesn't store the namespace properly for such packages, so even though the package file could be fetched from the external, Spack is unable to locate it. This commit avoids the issue by skipping any attempt to locate and copy from the package repository of externals, regardless of whether they have a Spack repo directory.
2020-07-10add public spack mirror (#17077)Peter Scheibel1-0/+2
2020-07-10bugfix: no infinite recursion in setup-env.sh on CrayTodd Gamblin3-0/+29
On Cray platforms, we rely heavily on the module system to figure out what targets, compilers, etc. are available. This unfortunately means that we shell out to the `module` command as part of platform initialization. Because we run subcommands in a shell, we can get infinite recursion if `setup-env.sh` and friends are in some init script like `.bashrc`. This fixes the infinite loop by adding guards around `setup-env.sh`, `setup-env.csh`, and `setup-env.fish`, to prevent recursive initializations of Spack. This is safe because Spack never shells out to itself, so we do not need it to be initialized in subshells. - [x] add recursion guard around `setup-env.sh` - [x] add recursion guard around `setup-env.csh` - [x] add recursion guard around `setup-env.fish`
2020-07-10Fix gcc + binutils compilation. (#9024)cedricchevalier191-3/+1
* fix binutils deptype for gcc binutils needs to be a run dependency of gcc * Fix gcc+binutils build on RHEL7+ static-libstdc++ is not available with system gcc. Anyway, as it is for bootstraping, we do not really care depending on a shared libstdc++. Co-authored-by: Michael Kuhn <michael@ikkoku.de>
2020-07-10autotools bugfix: handle missing config.guess (#17356)Michael Kuhn1-2/+2
Spack was attempting to calculate abspath on the located config.guess path even when it was not found (None); this commit skips the abspath calculation when config.guess is not found.
2020-07-10inel-mpi: fix for wrong structure name instroduced in ea8a0be4 (#17382)TZ1-1/+1
it's mpi_compiler_wrappers and not mpi_compiler._wrappers fixes 2nd part of #17371
2020-07-10Fix Intel MPI super invocation, again (#17378)Adam J. Stewart1-1/+1
2020-07-10autotools: Fix config.guess detection, take two (#17333)Michael Kuhn1-5/+3
The previous fix from #17149 contained a thinko that produced errors for packages that overwrite configure_directory.
2020-07-10spack install: improve error message with no args (#17454)Greg Becker2-2/+37
The error message was not updated when the behavior of Spack environments was changed to not automatically activate the local environment in #17258. The previous error message no longer makes sense.
2020-07-10Update the bbcp package (#17436)Rémi Lacroix1-3/+4
* bbcp: Update the URLs to use HTTPS. The HTTP URLs do not work anymore. * bbcp: Add missing libnsl dependency. * bbcp: Rename the git-based version to match the branch name. Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-07-10py-pysam: add LDFLAGS to curl (#17434)ketsubouchi1-0/+3
* py-pysam: add LDFLAGS to curl * Update var/spack/repos/builtin/packages/py-pysam/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-07-10grpc: add versions 1.28/1.29/1.30 (#17433)figroc1-3/+9
2020-07-10New packages: thepeg, herwig++ (2.x) (#17443)iarspider7-0/+376
* New packages: Rivet, Herwig++ 2 * Add patches for thepeg * Flake-8 * Update package.py * Delete thepeg-2.1.6.patch * Delete thepeg-2.1.5.patch * Delete thepeg-2.1.3.patch * Delete thepeg-2.2.0.patch
2020-07-10New packages: looptools + vbfnlo (#17446)iarspider2-0/+68
* New package: vbfnlo * Add new package: vbfnlo * Add recipe for looptools * Add patch for looptools * LoopTools: patch not needed (fixed by developers without changing version) * Remove patch file as well * Update package.py * Update package.py * Fix vbfnlo recipe for old version Co-authored-by: iarspider <iarpsider@gmail.com>
2020-07-10New Package: ChaNGa (#17442)Julius-Plehn3-2/+61
* WIP: changa package * changa cleanup * flake8 format * adds master branch to ChaNGa * positional arguments * use install instead of copy
2020-07-09Relocation of sbang needs to be done when the spack prefix changes even if ↵Patrick Gartung2-4/+17
the install tree has not changed. (#17455)
2020-07-09ltrace: Disable "-Werror". (#17444)Rémi Lacroix1-0/+5
Some functions used by ltrace have been deprecated in recent versions of glibc.
2020-07-09openslide: Add missing dependencies. (#17445)Rémi Lacroix1-0/+3
2020-07-09aspirin for buildaches (#17437)Harmen Stoppels1-1/+1
2020-07-09clear mpicc and friends before each build (#17450)Sajid Ali1-0/+8
* clear mpi env vars
2020-07-09installation: skip repository metadata for externals (#16954)Greg Becker1-3/+8
When Spack installs a package, it stores repository package.py files for it and all of its dependencies - any package with a Spack metadata directory in its installation prefix. It turns out this was too broad: this ends up including external packages installed by Spack (e.g. installed by another Spack instance). Currently Spack doesn't store the namespace properly for such packages, so even though the package file could be fetched from the external, Spack is unable to locate it. This commit avoids the issue by skipping any attempt to locate and copy from the package repository of externals, regardless of whether they have a Spack repo directory.
2020-07-08add public spack mirror (#17077)Peter Scheibel1-0/+2
2020-07-08new package: ligra (#17425)Sinan1-0/+44
* new package: ligra * setup run environment * tidy up * Update var/spack/repos/builtin/packages/ligra/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/ligra/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/ligra/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * flake8 Co-authored-by: Sinan81 <sbulut@3vgeomatics.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-07-08enable flatcc to be built with gcc@9.X.X (#17430)Frank Willmore1-0/+3
`gcc` 9 and above have more warnings that break the `flatcc` build by default, because `-Werror` is enabled. This loosens the build up so that we can build with more compilers in Spack. - [x] Add `-DFLATCC_ALLOW_WERROR=OFF` to `flatcc` CMake arguments Co-authored-by: Frank Willmore <willmore@anl.gov>
2020-07-08Buildcache: bindist test without invoking spack compiler wrappers. (#15687)Patrick Gartung8-9/+911
* Buildcache: * Try mocking an install of quux, corge and garply using prebuilt binaries * Put patchelf install after ccache restore * Add script to install patchelf from source so it can be used on Ubuntu:Trusty which does not have a patchelf pat package. The script will skip building on macOS * Remove mirror at end of bindist test * Add patchelf to Ubuntu build env * Revert mock patchelf package to allow other tests to run. * Remove depends_on('patchelf', type='build') relying instead on * Test fixture to ensure patchelf is available. * Call g++ command to build libraries directly during test build * Flake8 * Install patchelf in before_install stage using apt unless on Trusty where a build is done. * Add some symbolic links between packages * Flake8 * Flake8: * Update mock packages to write their own source files * Create the stage because spec search does not create it any longer * updates after change of list command arguments * cleanup after merge * flake8
2020-07-08Add missing file (#17426)iarspider1-0/+60
Co-authored-by: Ivan Razumov <ivan.razumov@cern.ch>
2020-07-08r-usethis: new version and dependencies (#17411)Amjad Kotobi1-1/+6
* r-usethis: new version and dependencies * r-usethis: fix in dependency
2020-07-08Ginkgo: new versions (#17413)tcojean2-0/+14
* Add new Ginkgo versions with HIP support. * Drop HIP support until more ROCm packages are integrated.
2020-07-08spack create: ask how many to download (#17373)Adam J. Stewart3-4/+8
2020-07-08typhon: fix build with Fujitsu compilers (#17424)ketsubouchi1-0/+4
2020-07-08ncl: fix compilation errors with Intel compilers (#17391)TZ1-1/+3
The Intel compilers are more strict and require special command line options (like -std=c99) to properly compile NCL.
2020-07-08Improve Travis sample in the docs (#17420)Simon Byrne1-3/+4
- printf is better than echo for multiline strings - ** should be && - use line continuation - Use multiline block
2020-07-07Fix YODA and Rivet recipes (#17412)iarspider2-6/+53
* Fix Rivet recipe; restrict Yoda versions for a give Rivet version * Fix YODA recipe * More tweaks to YODA version requirements * Flake-8
2020-07-07Relocate rpaths for all binaries, then do text bin replacement if the rpaths ↵Patrick Gartung1-7/+10
still exist after running patchelf/otool (#17418)
2020-07-07oneDNN: add v1.5.1 (#17419)Adam J. Stewart1-1/+2
2020-07-07GDAL: add v3.1.2 (#17416)Adam J. Stewart1-1/+2
2020-07-07CudaPackage: maintainers are listed in the docstring (#17409)Massimiliano Culpo1-1/+2
fixes #17396 This prevents the class attribute to be inherited and saves current maintainers from becoming the default maintainers of every Cuda package.
2020-07-07releases: document `releases/latest` tag (#17402)Todd Gamblin2-32/+61
We got rid of `master` after #17377, but users still want a way to get the latest stable release without knowing its number. We've added a `releases/latest` tag to replace what was once `master`. Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2020-07-07Uninstall: tolerate hook failures when force=true (#16513)Peter Scheibel1-2/+32
Fixes #16478 This allows an uninstall to proceed even when encountering pre-uninstall hook failures if the user chooses the --force option for the uninstall. This also prevents post-uninstall hook failures from raising an exception, which would terminate a sequence of uninstalls. This isn't likely essential for #16478, but I think overall it will improve the user experience: if the post-uninstall hook fails, there isn't much point in terminating a sequence of spec uninstalls because at the point where the post-uninstall hook is run, the spec has already been removed from the database (so it will never have another chance to run). Notes: * When doing spack uninstall -a, certain pre/post-uninstall hooks aren't important to run, but this isn't easy to track with the current model. For example: if you are uninstalling a package and its extension, you do not have to do the activation check for the extension. * This doesn't handle the uninstallation of specs that are not in the DB, so it may leave "dangling" specs in the installation prefix