Age | Commit message (Collapse) | Author | Files | Lines |
|
When adding an Environment to a user's shell, Spack was only adding
root specs. This now includes run dependencies of root specs.
|
|
* gobject-introspection: fix for Python 3.9.
* Fixes the too long line formatting issue.
* gobject-introspection: limits the scope of the patch
Co-authored-by: Robert Mijakovic <robert.mijakovic@lxp.lu>
|
|
Variants explicitly set in an abstract root spec are considered
as defaults for the package they refer to, and they override
what is in packages.yaml and in package.py. This is relevant
only for multi-valued variants, where a constraint may extend
an already default value.
|
|
* Fixes to flex
- Prefer the version that doesn't need all the patches and extra build
tools
- Make dependency on gettext optional under the nls variant (off by
default)
- Drop the dependency on help2man if we don't have to regenerate the man
pages (when no patches are necessary)
* Bring back gettext dep as it is used during autoconf
|
|
Co-authored-by: Robert Mijakovic <robert.mijakovic@lxp.lu>
|
|
|
|
|
|
|
|
Disable mpi search when using cce (the CCE compiler wrappers do not behave like the conventional mpi compiler wrappers).
|
|
Add darshan-3.3.0 tags to darshan util/runtime, AutoPerf variants, AutoPerf XC variants, and HDF5 module support to darshan-runtime.
|
|
* Enhancing package gmsh to more options, new version
* Enhancing package gmsh, url from https
* Enhancing package gmsh, following reviewer 1
* Improving package gmsh from reviewer
* Adding MED dependency
* Removing env variables and unused dependency (netgen/tetgen)
|
|
Enhancing package med enlarged HDF5 compatibility, more options, new version
|
|
|
|
only parses the version, variant parsing will follow.
|
|
|
|
Force CCE to compile fortran modules with lower case names, allow for CCE to be the host compiler with nvcc
|
|
|
|
|
|
A proposed fix for #23436
|
|
|
|
|
|
|
|
add -Wno-final-dtor-non-final-class flag
|
|
Add the latest release of WarpX.
|
|
When building with CCE, do not use the -Werror flag
|
|
when using Cray's cs-prgenv, allow the build system to detect the systems as an XC
|
|
remove -Werror flag when compiling with cce
|
|
|
|
|
|
|
|
|
|
|
|
`flag_handler` currently passes all flags via injection. This makes it
impossible to override the default flags provided by autotools (for
instance, `binutils cflags='-O2'` will still build with `-O2 -g`).
Instead, use injection for our workaround flags and pass other flags to
the build system.
|
|
|
|
|
|
* craype fix for pdt
adapt the pdt package for cce
* fix style issues
|
|
|
|
allow cce to be the compiler
|
|
* Disable link-time optimization for matplotlib when using Clang.
* Remove duplicated line.
* Disable LTO only for versions >= 3.3.0.
|
|
Add conflict for the CCE compiler
|
|
* geos: Fix config issues with python bindings using python3 (#23479)
This should fix some config issues when building geos with python
bindings and using python3 --- the geos configuration scripts had
a few python2-isms.
I only tested (lightly; geos built and I can import geos in python3)
on 3.8.1, but I did check that the patch can at least be applied
in 3.5.
I belatedly discovered that geos dropped all the SWIG bindings
in @3.9, so I also added some conflicts on the +python and +ruby
options to note that they are not supported in 3.9.
* geos: adding omitted patch file
|
|
match with a root spec as well as with a dependency of a root spec
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Robert Mijakovic <robert.mijakovic@lxp.lu>
|
|
Co-authored-by: Robert Mijakovic <robert.mijakovic@lxp.lu>
|
|
|
|
Added the checksum for 4.1.2 and 4.2.0
The `parallel` variant did the exact same behavior as the `mpi` variant, but they had different default values than each other. Both variants set the value of `-DCGNS_ENABLE_PARALLEL`, so it was unclear which variant was "winning" and could definitely result in a non-intuitive build. Did a grep of the spack packages and none of them where using the `parallel` variant to control the cgns options. Retained the `mpi` variant as that one is being used by multiple packages.
One issue that remains to be solved is that the default integer size has changed from 32-bit to 64-bit for the 4.2.0 release. This is controlled by the `int64` variant which currently defaults to `OFF`. There should maybe be some thought about changing the default to match the default of the current release, or maybe having a version-specific default... For now, left the behavior as it has been for previous versions.
|