Files
spack/var/spack/repos/builtin/packages/adios/package.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

181 lines
6.9 KiB
Python
Raw Normal View History

# Copyright 2013-2023 Lawrence Livermore National Security, LLC and other
# Spack Project Developers. See the top-level COPYRIGHT file for details.
#
# SPDX-License-Identifier: (Apache-2.0 OR MIT)
from spack.package import *
2016-06-26 22:00:10 +02:00
class Adios(AutotoolsPackage):
2016-08-24 10:32:29 -05:00
"""The Adaptable IO System (ADIOS) provides a simple,
2016-06-26 22:00:10 +02:00
flexible way for scientists to describe the
data in their code that may need to be written,
read, or processed outside of the running simulation.
"""
2016-06-26 22:00:10 +02:00
start of work to add spack audit packages-https checker (#25670) This PR will add a new audit, specifically for spack package homepage urls (and eventually other kinds I suspect) to see if there is an http address that can be changed to https. Usage is as follows: ```bash $ spack audit packages-https <package> ``` And in list view: ```bash $ spack audit list generic: Generic checks relying on global variables configs: Sanity checks on compilers.yaml Sanity checks on packages.yaml packages: Sanity checks on specs used in directives packages-https: Sanity checks on https checks of package urls, etc. ``` I think it would be unwise to include with packages, because when run for all, since we do requests it takes a long time. I also like the idea of more well scoped checks - likely there will be other addresses for http/https within a package that we eventually check. For now, there are two error cases - one is when an https url is tried but there is some SSL error (or other error that means we cannot update to https): ```bash $ spack audit packages-https zoltan PKG-HTTPS-DIRECTIVES: 1 issue found 1. Error with attempting https for "zoltan": <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'www.cs.sandia.gov'. (_ssl.c:1125)> ``` This is either not fixable, or could be fixed with a change to the url or (better) contacting the site owners to ask about some certificate or similar. The second case is when there is an http that needs to be https, which is a huge issue now, but hopefully not after this spack PR. ```bash $ spack audit packages-https xman Package "xman" uses http but has a valid https endpoint. ``` And then when a package is fixed: ```bash $ spack audit packages-https zlib PKG-HTTPS-DIRECTIVES: 0 issues found. ``` And that's mostly it. :) Signed-off-by: vsoch <vsoch@users.noreply.github.com> Co-authored-by: vsoch <vsoch@users.noreply.github.com>
2021-09-02 00:46:27 -06:00
homepage = "https://www.olcf.ornl.gov/center-projects/adios/"
url = "https://github.com/ornladios/ADIOS/archive/v1.12.0.tar.gz"
git = "https://github.com/ornladios/ADIOS.git"
maintainers("ax3l")
version("develop", branch="master")
version("1.13.1", sha256="b1c6949918f5e69f701cabfe5987c0b286793f1057d4690f04747852544e157b")
version("1.13.0", sha256="7b5ee8ff7a5f7215f157c484b20adb277ec0250f87510513edcc25d2c4739f50")
version("1.12.0", sha256="22bc22c157322abec2d1a0817a259efd9057f88c2113e67d918a9a5ebcb3d88d")
version("1.11.1", sha256="9f5c10b9471a721ba57d1cf6e5a55a7ad139a6c12da87b4dc128539e9eef370e")
version("1.11.0", sha256="e89d14ccbe7181777225e0ba6c272c0941539b8ccd440e72ed5a9457441dae83")
version("1.10.0", sha256="6713069259ee7bfd4d03f47640bf841874e9114bab24e7b0c58e310c42a0ec48")
version("1.9.0", sha256="23b2bb70540d51ab0855af0b205ca484fd1bd963c39580c29e3133f9e6fffd46")
variant("shared", default=True, description="Builds a shared version of the library")
variant("fortran", default=False, description="Enable Fortran bindings support")
variant("mpi", default=True, description="Enable MPI support")
variant("infiniband", default=False, description="Enable infiniband support")
# transforms
variant("zlib", default=True, description="Enable zlib transform support")
variant("bzip2", default=False, description="Enable bzip2 transform support")
variant("szip", default=False, description="Enable szip transform support")
variant("zfp", default=True, description="Enable ZFP transform support")
variant("sz", default=True, description="Enable SZ transform support")
variant("lz4", default=True, description="Enable LZ4 transform support")
variant("blosc", default=True, description="Enable Blosc transform support")
# transports and serial file converters
variant(
"hdf5",
default=False,
description="Enable parallel HDF5 transport and serial bp2h5 " + "converter",
)
variant("netcdf", default=False, description="Enable netcdf support")
variant(
Multi-valued variants: better support for combinations (#9481) This enforces conventions that allow for correct handling of multi-valued variants where specifying no value is an option, and adds convenience functionality for specifying multi-valued variants with conflicting sets of values. This also adds a notion of "feature values" for variants, which are those that are understood by the build system (e.g. those that would appear as configure options). In more detail: * Add documentation on variants to the packaging guide * Forbid usage of '' or None as a possible variant value, in particular as a default. To indicate choosing no value, the user must explicitly define an option like 'none'. Without this, multi-valued variants with default set to None were not parsable from the command line (Fixes #6314) * Add "disjoint_sets" function to support the declaration of multi-valued variants with conflicting sets of options. For example a variant "foo" with possible values "a", "b", and "c" where "c" is exclusive of the other values ("foo=a,b" and "foo=c" are valid but "foo=a,c" is not). * Add "any_combination_of" function to support the declaration of multi-valued variants where it is valid to choose none of the values. This automatically defines "none" as an option (exclusive with all other choices); this value does not appear when iterating over the variant's values, for example in "with_or_without" (which constructs autotools option strings from variant values). * The "disjoint_sets" and "any_combination_of" methods return an object which tracks the possible values. It is also possible to indicate that some of these values do not correspond to options understood by the package's build system, such that methods like "with_or_without" will not define options for those values (this occurs automatically for "none") * Add documentation for usage of new functions for specifying multi-valued variants
2019-01-05 04:02:34 +01:00
"staging",
values=any_combination_of("flexpath", "dataspaces"),
description="Enable dataspaces and/or flexpath staging transports",
)
depends_on("autoconf", type="build")
depends_on("automake", type="build")
depends_on("m4", type="build")
depends_on("libtool", type="build")
depends_on("python", type="build")
2016-08-29 18:42:07 +02:00
depends_on("mpi", when="+mpi")
# optional transformations
depends_on("zlib-api", when="+zlib")
depends_on("bzip2", when="+bzip2")
depends_on("szip", when="+szip")
depends_on("sz@:1.4.10", when="@:1.12.0 +sz")
depends_on("sz@1.4.11.0:1.4.11", when="@1.13.0 +sz")
depends_on("sz@1.4.12.3:1.4.12", when="@1.13.1: +sz")
depends_on("zfp@0.5.1:0.5", when="+zfp")
depends_on("lz4", when="+lz4")
depends_on("c-blosc@1.12.0:", when="+blosc")
# optional transports & file converters
depends_on("hdf5@1.8:+hl+mpi", when="+hdf5")
depends_on("netcdf-c", when="+netcdf")
depends_on("libevpath", when="staging=flexpath")
depends_on("dataspaces+mpi", when="staging=dataspaces")
for p in ["+hdf5", "+netcdf", "staging=flexpath", "staging=dataspaces"]:
conflicts(p, when="~mpi")
build_directory = "spack-build"
# ADIOS uses the absolute Python path, which is too long and results in
# "bad interpreter" errors - but not applicable for 1.9.0
patch("python.patch", when="@1.10.0:")
# Fix ADIOS <=1.10.0 compile error on HDF5 1.10+
# https://github.com/ornladios/ADIOS/commit/3b21a8a41509
# https://github.com/spack/spack/issues/1683
patch("adios_1100.patch", when="@:1.10.0^hdf5@1.10:")
# ADIOS 1.13.1 is written for ZFP 0.5.0 interfaces
# https://github.com/ornladios/ADIOS/pull/204
patch("zfp051.patch", when="@1.11.0:1.13.1")
# Fix a bug in configure.ac that causes automake issues on RHEL 7.7
patch(
"https://github.com/ornladios/ADIOS/pull/207.patch?full_index=1",
when="@1.12.0: +mpi",
sha256="aea47e56013b57c2d5d36e23e0ae6010541c3333a84003784437768c2e350b05",
)
def validate(self, spec):
"""Checks if incompatible variants have been activated at the same time
Args:
spec: spec of the package
Raises:
RuntimeError: in case of inconsistencies
"""
if "+fortran" in spec and not self.compiler.fc:
msg = "cannot build a fortran variant without a fortran compiler"
raise RuntimeError(msg)
def with_or_without_hdf5(self, activated):
if activated:
2023-10-11 10:47:42 -07:00
return f"--with-phdf5={self.spec['hdf5'].prefix}"
return "--without-phdf5"
2020-05-11 23:54:08 +02:00
def setup_build_environment(self, env):
# https://github.com/ornladios/ADIOS/issues/206
if self.spec.satisfies("%gcc@10: +fortran"):
env.set("FCFLAGS", "-fallow-argument-mismatch")
def configure_args(self):
spec = self.spec
self.validate(spec)
extra_args = [
# required, otherwise building its python bindings will fail
2023-10-11 10:47:42 -07:00
f"CFLAGS={self.compiler.cc_pic_flag}"
]
extra_args += self.enable_or_disable("shared")
extra_args += self.enable_or_disable("fortran")
if "+mpi" in spec:
env["MPICC"] = spec["mpi"].mpicc
env["MPICXX"] = spec["mpi"].mpicxx
extra_args += self.with_or_without("mpi", activation_value="prefix")
extra_args += self.with_or_without("infiniband")
if "+zlib" in spec:
2023-10-11 10:47:42 -07:00
extra_args.append(f"--with-zlib={spec['zlib-api'].prefix}")
else:
extra_args.append("--without-zlib")
# Transforms
variants = ["bzip2", "szip"]
if spec.satisfies("@1.11.0:"):
variants += ["zfp"]
if spec.satisfies("@1.12.0:"):
variants += ["sz", "lz4"]
if spec.satisfies("@1.13.0:"):
extra_args += self.with_or_without(
"blosc", activation_value=lambda x: spec["c-blosc"].prefix
)
# External I/O libraries
variants += ["hdf5", "netcdf"]
for x in variants:
extra_args += self.with_or_without(x, activation_value="prefix")
# Staging transports
def with_staging(name):
if name == "flexpath":
return spec["libevpath"].prefix
return spec[name].prefix
extra_args += self.with_or_without("staging", activation_value=with_staging)
return extra_args