summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-06-19py-pkginfo: add 1.9.6 (#38434)Manuela Kuhn1-2/+2
* py-pkginfo: add 1.9.6 * Remove py-setuptools as run dependency
2023-06-19gsl: set GSL_ROOT_DIR (#38464)Juan Miguel Carceller1-0/+5
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com> Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2023-06-19repeatmasker: adding version 4.1.5 (#38445)snehring1-0/+1
2023-06-19py-pooch: add 1.7.0 (#38466)Manuela Kuhn1-3/+11
2023-06-19spdlog: patch for fmt::basic_runtime when ^fmt@10 (#38082)Wouter Deconinck1-0/+7
2023-06-18cc: Ensure that user-specified flags take precedence over others (#37376)Andrey Parfenov2-195/+256
Spack flags supplied by users should supersede flags from package build systems and other places in Spack. However, Spack currently adds user-supplied flags to the beginning of the compile line, which means that in some cases build system flags will supersede user-supplied ones. The right place to add a flag to ensure it has highest precedence for the compiler really depends on the type of flag. For example, search paths like `-L` and `-I` are examined in order, so adding them first is highest precedence. Compilers take the *last* occurrence of optimization flags like `-O2`, so those should be placed *after* other such flags. Shim libraries with `-l` should go *before* other libraries on the command line, so we want user-supplied libs to go first, etc. `lib/spack/env/cc` already knows how to split arguments into categories like `libs_list`, `rpath_dirs_list`, etc., so we can leverage that functionality to merge user flags into the arg list correctly. The general rules for injected flags are: 1. All `-L`, `-I`, `-isystem`, `-l`, and `*-rpath` flags from `spack_flags_*` to appear before their regular counterparts. 2. All other flags ordered with the ones from flags after their regular counterparts, i.e. `other_flags` before `spack_flags_other_flags` - [x] Generalize argument categorization into its own function in the `cc` shell script - [x] Apply the same splitting logic to injected flags and flags from the original compile line. - [x] Use the resulting flag lists to merge user- and build-system-supplied flags by category. - [x] Add tests. Signed-off-by: Andrey Parfenov <andrey.parfenov@intel.com> Co-authored-by: iermolae <igor.ermolaev@intel.com>
2023-06-18fix oneapi modules (#38400)simonleary-umass-edu1-1/+1
2023-06-18py-vermin: add latest version 1.5.2 (#38460)Morten Kristensen1-3/+3
* py-vermin: add latest version 1.5.2 * Removed obsolete dep and setuptools is only for build-time - setuptools are not used as runtime - py27 isn't strictly necessary
2023-06-17Add latest enzyme release (#38442)William Moses1-3/+5
2023-06-16unparser: drop Python 2, fix testing bugs with newer Pythons (#38424)Greg Becker2-129/+20
The `unparser` that Spack uses for package hashing had several tweaks to ensure compatibility with Python 2.7: 1. Currently, the unparser automatically moves `*` and `**` args to the end to preserve compatibility with `python@:3.4` 2. `print a, b, c` statements and single-tuple `print((a, b, c))` function calls were remapped to `print(a, b, c)` in the unparsed output for consistency across versions. (1) is causing issues in our tests because a recent patch to the Python source code (https://github.com/python/cpython/pull/102953/files#diff-7972dffec6674d5f09410c71766ac6caacb95b9bccbf032061806ae304519c9bR813-R823) has a `**` arg before an named argument, and we round-trip the core python source code as a test of our unparser. This isn't actually a break with our consistent unpausing -- it's still consistent, the python source just doesn't unparse to the same thing anymore. It does makes it harder to test, so it's not worth maintaining the Python2-specific stuff anymore. Since we only support `python@3.6:`, this PR removes (1) and (2) from the unparser, but keeps one last tweak for unicode AST inconsistencies, as it's still needed for Python 3.5-3.7. This fixes the CI error we've been seeing on `python@3.11.4` and `python@3.10.12`. Again, that bug exists only in the test system and doesn't affect our canonical hashing of Python code.
2023-06-16py-aiohttp: add 3.8.4 (#38451)Manuela Kuhn1-15/+18
2023-06-16millepede: add v04-13-03 (#38141)Alec Scott1-0/+1
2023-06-16show external status as [e] (#33792)Greg Becker2-14/+34
2023-06-16WarpX 23.06 (#38303)Axel Huebl5-30/+63
* WarpX 23.06 Update WarpX and related Python packages to the lastest releases. WarpX 23.06 introduces multi-dimension support in a single package, which will ease deployment in E4S et al. that can ship now a single, full-feature module/package that is NOT incompatible with itself anymore. * e4s ci stacks: multiple specs for each dim variant no longer required * [@spackbot] updating style on behalf of ax3l * WarpX: Update CMake CLI and Test/Check * Add Missing `build-directory` * [@spackbot] updating style on behalf of ax3l * Remove `build_directory` again --------- Co-authored-by: eugeneswalker <eugenesunsetwalker@gmail.com> Co-authored-by: ax3l <ax3l@users.noreply.github.com>
2023-06-16docs: add quotes around some values in a YAML example (#38412)Gurkirat Singh1-3/+3
2023-06-15Remove experimental hdf5 versions 1.13.x and add hdf5 version 1.10.10. (#38013)Larry Knox5-12/+8
* Remove experimental hdf5 versions 1.13.x. Upgrade to 1.14 or remove dependencies on hdf5 1.13.x. * Revert change to netcdf-c/package.py.
2023-06-15star: add 2.7.10 (#38197)George Young1-4/+15
* star: add 2.7.10 * star: fix building for non-avx2 arch processors * convert to MakefilePackage, second take at fixing for aarch64 * style --------- Co-authored-by: LMS Bioinformatics <bioinformatics@lms.mrc.ac.uk>
2023-06-15perl-gd: update to 2.77, update urls (#38413)George Young1-1/+9
* perl-gd: update to 2.77, update urls --------- Co-authored-by: LMS Bioinformatics <bioinformatics@lms.mrc.ac.uk>
2023-06-15Enable build system guess tests on windows (#36971)markus-ferrell2-5/+1
2023-06-15MXNet: fix flag versions (#38402)Adam J. Stewart1-2/+2
2023-06-15Windows testing: enable graph, mark, and info cmd tests (#36977)markus-ferrell3-11/+0
2023-06-15Create package.py file for NIMROD abstract accelerated infrastructure. (#38405)Jacob King1-0/+58
Co-authored-by: jacobrking <jacobrking@users.noreply.github.com>
2023-06-15py-nibabel: add 5.1.0 (#38379)Manuela Kuhn1-2/+12
2023-06-15podio: Add py-tabulate as new run and test dependency (#38409)Thomas Madlener1-0/+1
2023-06-15py-numba: add 0.57.0, update dependency ranges (#38390)George Young1-5/+7
* py-numba: add 0.57.0, update dependency ranges * Update var/spack/repos/builtin/packages/py-numba/package.py Co-authored-by: Manuela Kuhn <36827019+manuelakuhn@users.noreply.github.com> * Update var/spack/repos/builtin/packages/py-numba/package.py Co-authored-by: Manuela Kuhn <36827019+manuelakuhn@users.noreply.github.com> * Update package.py --------- Co-authored-by: LMS Bioinformatics <bioinformatics@lms.mrc.ac.uk> Co-authored-by: Manuela Kuhn <36827019+manuelakuhn@users.noreply.github.com>
2023-06-15py-datalad: add 0.18.4 (#37936)Manuela Kuhn1-1/+3
2023-06-15tests/py-horovod: convert to new stand-alone test process (#38366)Tamara Dahlgren1-3/+4
2023-06-15tests/py-libensemble: convert to new stand-alone test process (#38344)Tamara Dahlgren1-20/+16
2023-06-15tests/py-eccodes: convert to new stand-alone test process (#38346)Tamara Dahlgren1-9/+4
2023-06-15py-neurora: add 1.1.6.10 (#38378)Manuela Kuhn1-0/+1
2023-06-15Add virtual information on DAG edges (#34821)Massimiliano Culpo18-136/+290
* DependencySpec: add virtuals attribute on edges This works for both the new and the old concretizer. Also, added type hints to involved functions. * Improve virtual reconstruction from old format * Reconstruct virtuals when reading from Cray manifest * Reconstruct virtual information on test dependencies
2023-06-14test/dust: convert to new stand-alone test process (#38367)Tamara Dahlgren1-9/+5
2023-06-14py-nbclient: add 0.8.0 (#38325)Manuela Kuhn1-1/+3
2023-06-14py-nbconvert: add 7.4.0 (#38326)Manuela Kuhn1-19/+20
* py-nbconvert: add 7.4.0 * Move historical dependencies after variant
2023-06-14py-docutils: re-add python@3.7 (#38336)Manuela Kuhn1-0/+1
2023-06-14magma@master: add python dependency (#38341)Satish Balay1-0/+1
2023-06-14edm4hep: Add version 0.9 (#38205)Thomas Madlener1-0/+1
2023-06-14fairmq: Add v1.6.0 (#38392)Dennis Klein1-0/+7
2023-06-14ltp: add v20230516 (#38138)Alec Scott1-0/+1
2023-06-14subread: add 2.0.6, update download paths (#38200)George Young1-4/+4
* subread: add 2.0.6, update download paths * Update var/spack/repos/builtin/packages/subread/package.py --------- Co-authored-by: LMS Bioinformatics <bioinformatics@lms.mrc.ac.uk> Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2023-06-14openradioss-starter,engine: new package (#38291)kjrstory2-0/+256
* openradioss-starter,engine: new package * openradioss-engine: change version name develop to main * openradioss-starter: change version name develop to main
2023-06-14freeipmi: add v1.6.9 (#38349)Alec Scott1-0/+1
2023-06-14Add Binder spackage (#38371)Kim Liegeois1-0/+54
* Add Binder spackage * Format binder recipe * Format binder recipe
2023-06-14add bioconductor-ebseq (#38380)pabloaledo1-0/+29
* add buiconductor-ebseq Signed-off-by: Pablo <pablo.aledo@seqera.io> --------- Signed-off-by: Pablo <pablo.aledo@seqera.io>
2023-06-14ctffind: Add a patch to fix incorrect return types. (#38085)RĂ©mi Lacroix2-0/+35
Prevent the code from crashing (cf. https://grigoriefflab.umassmed.edu/comment/1696#comment-1696).
2023-06-14dsqss: convert to new stand-alone test process (#38372)Tamara Dahlgren1-6/+15
2023-06-14lastz: add v1.04.22 (#38388)Alec Scott1-0/+2
* lastz: add v1.04.22 * Fix formatting of versions to include extra space
2023-06-14ipopt: add v3.14.9 (#38387)Alec Scott1-0/+1
2023-06-14imath: add v3.1.9 (#38386)Alec Scott1-0/+1
2023-06-14imagemagick: add v7.1.1-11 (#38385)Alec Scott1-0/+1