| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
* Add versions 3.4.4 through 4.1.0 and 4.1.0-openvino
* Add conflict for gcc version >= 7 when building with +cuda
* Later version of protobuf is required for later versions of OpenCV
* Explicitly remove protobuf dependency with CMake option when not
building with +dnn
|
|
* py-pauvr:new package
* falcon-unzip: new package
* supernova: updating
* masurca: updating
* rm extra files
* modifying available versions and adding url
* fixing deleted supernova
|
|
|
|
|
|
VTK requires a patched libharu that is not maintained upstream
See https://github.com/libharu/libharu/pull/157
|
|
|
|
Confirmed that versions before 2.7.5 do not require this dependency.
|
|
|
|
|
|
* root: new versions, variants and patches to bring in to line with FNAL's use.
* Support MySQL.
* Patches:
* Bigger stringbuf.
* Find MySQL even when it's called mariadb-c-client.
* Honor external provision of unuran.
* Properly handle the ROOT7 web GUI for 6.16/00.
* `memstat` variant is now default-OFF due to version-related constraints.
* Add missing dependencies.
* Propagate `python` to `libxml2`.
* Handle external FTGL dependency with X / OpenGL: depends on PR ####
* Force `SPACK_INCLUDE_DIRS` to avoid warning.
* New `gminimal` variant default ON per discussion with Javier Cervantes.
* Style fixes per flake8.
* Remove redundant `PATH_SUFFIX` per https://github.com/root-project/root/pull/1993#discussion_r276840329
* Comment patches per https://github.com/spack/spack/pull/11215#discussion_r276887199.
* Reflect the fact that MariaDB support patch is now upstream.
* Restore ncurses dependency for libtinfo.
|
|
Usage of double quotes was preventing word-splitting when parsing
module roots in setup-env.sh, which lead to an error when multiple
module roots are used (in particular when Spack is pointed to use
an upstream module root in addition to its own).
|
|
|
|
|
|
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.
|
|
* _valid_tokens list is missing a needed comma
|
|
* 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.
|
|
|
|
The squashfs Makefile's `INSTALL_DIR` args is the path to the `bin` directory, not the top of the install tree.
Adjust accordingly.
|
|
- Add link to container image, as well as a description of VMs
- Update slide link to point to latest RIKEN tutorial
|
|
|
|
- `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
|
|
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.
|
|
* Fix detection of LLVM-enabled PGI compilers
* Add unit tests for LLVM-enabled PGI compiler version detection
|
|
|
|
* 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
|
|
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).
|
|
Ref: https://github.com/dealii/dealii/issues/7934
|
|
|
|
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.
|
|
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).
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
* 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
|
|
|
|
|
|
|
|
#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.
|
|
|
|
|
|
|
|
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
|
|
* 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.
|
|
|
