summaryrefslogtreecommitdiff
path: root/var/spack/repos/builtin/packages/boost
AgeCommit message (Collapse)AuthorFilesLines
2024-01-02Update copyright year to 2024 (#41919)Todd Gamblin1-1/+1
It was time to run `spack license update-copyright-year` again.
2023-12-27Initial License CheckinAiden Grossman1-0/+2
This patch adds license information for about 5,300 packages from automated sources. The license information was obtained from Alpine Linux and PyPI and processed using tooling available in https://github.com/boomanaiden154/spack-license-utils. The license field was added in after all other directives in an automated fashion. Note that while this license information is probably fairly accurate, it is not guaranteed to be accurate. In addition some of the license strings from Alpine Linux might not be valid SPDX license strings. Invalid SPDX identifiers can be picked up and fixed once we have validation/parsing infrastructure in place for the solver, and issues can be fixed as they come up.
2023-09-27Trilinos package: build on Windows (#34622)Jared Popelar1-13/+26
Update Trilinos and dependencies to build a limited version of Trilinos on Windows. * Support trilinos~mpi~shared on Windows * superlu: force CMake build on Windows * boost: update to build on Windows (proper option formatting and build tool names) * pcre, openblas: add CMake-based build (keep prior build system as default on platforms other than Windows) * openblas: add patch when using Intel Fortran compiler (currently this is included as part of the hybrid %msvc compiler in Spack) Co-authored-by: John Parent <john.parent@kitware.com>
2023-09-20Add 23 and 26 to the cxxstd variant for boost (#40081)Auriane R1-1/+3
2023-09-05boost: support variant cxxstd=20 (#39769)Wouter Deconinck1-0/+1
2023-08-17boost %oneapi: add cxxflags -Wno-error=enum-constexpr-conversion (#39477)eugeneswalker1-0/+6
2023-08-14Add Boost 1.83.0 (#39415)Mikael Simberg1-0/+1
2023-08-09zlib-api: new virtual with zlib/zlib-ng as providers (#37372)Harmen Stoppels1-3/+3
Introduces a new virtual zlib-api, which replaces zlib in most packages. This allows users to switch to zlib-ng by default for better performance.
2023-04-24Extend patch to 1.82.0 (#37138)Juan Miguel Carceller1-1/+1
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com>
2023-04-17Boost: add version 1.82.0 (#36924)Tim Haines1-0/+8
2023-03-29Fix dyninst build with old boost (#36198)Massimiliano Culpo1-4/+3
Fix patching old boost versions to account for builders. Add a proper version constraint on boost for recent dyninst. The constraint can be found in dyninst source code under "cmake/Boost.cmake" which contains: set(_boost_min_version 1.70.0) Co-authored-by: Greg Becker <becker33@llnl.gov>
2023-03-17boost: add patch for 1.81.0 (#35964)Valentin Volkl2-0/+35
2023-03-08boost: add v1.81.0 (#34613)Tim Haines1-0/+1
2023-02-01Use the `maintainers` directive in all packages (#35201)Massimiliano Culpo1-1/+1
2023-01-18license year bump (#34921)Harmen Stoppels1-1/+1
* license bump year * fix black issues of modified files * mypy * fix 2021 -> 2023
2022-12-29boost: apply 'intel-oneapi-linux-jam.patch' to all versions since 1.76 (#34670)Tim Haines1-1/+1
2022-11-23ecflow: polish recipe (#34043)Massimiliano Culpo1-0/+3
2022-11-23boost: At least with older Xcode, boost can't build with lzma (#34075)Bernhard Kaindl1-0/+3
Reference: https://lists.boost.org/Archives/boost/2019/11/247380.php As reported at the end of #33998 and this link, liblzma on older Xcode on MacOSX 10 misses _lzma_cputhreads, so boost's can't use liblzma on those.
2022-11-19Boost: enable lzma and zstd iostreams (#33998)iarspider1-2/+8
2022-11-09Boost: Change comment to conflict for MPI/Python (#33767)kwryankrattiger1-4/+7
Boost 1.64.0 has build errors when building the python and MPI modules. This was previously just a comment in the package.py which allowed broken specs to concretize. The comments are now expressed in conflicts to prevent this.
2022-10-20Add Boost 1.80.0 (#32879)Mikael Simberg1-0/+5
* Add Boost 1.80.0 * Add conflict for Boost 1.80.0 and dealii * Add conflict for Boost 1.80 and %oneapi
2022-08-12boost@1.76:1.79 %oneapi: patch according to Intel guide for building Boost ↵eugeneswalker2-1/+1
(#32097)
2022-07-31black: reformat entire repository with blackTodd Gamblin1-394/+422
2022-06-30boost: do not add the context-impl option for version below 1.65.0 (#30719)Max Zeyen1-2/+7
* boost: do not access the context-impl variant for versions below 1.65.0 * boost: check if spec.variants contains context-impl * boost: improve error message when the context-impl variant causes a conflict Executing spack solve boost@1.63.0 +context context-impl=fcontext triggers the following error message: ==> Error: No version for 'boost' satisfies '@1.63.0' and '@1.79.0' With this change, the error message becomes the following: ==> Error: Cannot set variant 'context-impl' for package 'boost' because the variant condition cannot be satisfied for the given spec
2022-05-28refactor: packages import `spack.package` explicitly (#30404)Tom Scogland1-1/+1
Explicitly import package utilities in all packages, and corresponding fallout. This includes: * rename `spack.package` to `spack.package_base` * rename `spack.pkgkit` to `spack.package` * update all packages in builtin, builtin_mock and tutorials to include `from spack.package import *` * update spack style * ensure packages include the import * automatically add the new import and remove any/all imports of `spack` and `spack.pkgkit` from packages when using `--fix` * add support for type-checking packages with mypy when SPACK_MYPY_CHECK_PACKAGES is set in the environment * fix all type checking errors in packages in spack upstream * update spack create to include the new imports * update spack repo to inject the new import, injection persists to allow for a deprecation period Original message below: As requested @adamjstewart, update all packages to use pkgkit. I ended up using isort to do this, so repro is easy: ```console $ isort -a 'from spack.pkgkit import *' --rm 'spack' ./var/spack/repos/builtin/packages/*/package.py $ spack style --fix ``` There were several line spacing fixups caused either by space manipulation in isort or by packages that haven't been touched since we added requirements, but there are no functional changes in here. * [x] add config to isort to make sure this is maintained going forward
2022-05-17boost: constrain context-impl variant (#30654)Tim Haines1-1/+1
2022-05-06boost: add support for alternate boost-context backends (#30496)Thomas Dickerson1-0/+20
The fcontext backend is the default high-performance backend. The ucontext backend is needed when using Boost context in conjunction with ASAN. The WinFibers backend...also exists. https://www.boost.org/doc/libs/1_79_0/libs/context/doc/html/context/cc/implementations__fcontext_t__ucontext_t_and_winfiber.html
2022-05-03boost: fix v1.78 build with oneapi (#30463)eugeneswalker2-0/+18
2022-04-26boost: update list of modules (#30104)Erik Schnetter1-5/+28
Co-authored-by: Tim Haines <thaines.astro@gmail.com>
2022-04-21boost: add v1.79.0 (#30137)Tim Haines1-0/+1
2022-04-10Remove versions 1.34.0:1.38.0 (#29983)Tim Haines1-6/+0
These versions have never been buildable because they do not include a 'bootstrap.sh' file.
2022-04-04Allow conditional possible values in variants (#29530)Massimiliano Culpo1-7/+7
Allow declaring possible values for variants with an associated condition. If the variant takes one of those values, the condition is imposed as a further constraint. The idea of this PR is to implement part of the mechanisms needed for modeling [packages with multiple build-systems]( https://github.com/spack/seps/pull/3). After this PR the build-system directive can be implemented as: ```python variant( 'build-system', default='cmake', values=( 'autotools', conditional('cmake', when='@X.Y:') ), description='...', ) ``` Modifications: - [x] Allow conditional possible values in variants - [x] Add a unit-test for the feature - [x] Add documentation
2022-03-30Add patch to fix compilation of boost with compilers not in path (#29718)Mikael Simberg2-0/+16
Co-authored-by: Mikael Simberg <mikael.simberg@iki.if>
2022-03-23Use stable URLs and `?full_index=1` for all github patches (#29239)Adam J. Stewart1-4/+4
The number of commit characters in patch files fetched from GitHub can change, so we should use `full_index=1` to enforce full commit hashes (and a stable patch `sha256`). Similarly, URLs for branches like `master` don't give us stable patch files, because branches are moving targets. Use specific tags or commits for those. - [x] update all github patch URLs to use `full_index=1` - [x] don't use `master` or other branches for patches - [x] add an audit check and a test for `?full_index=1` Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
2022-03-17Make boost minimal and composable (Original PR#22303) (#28623)Abhik Sarkar1-25/+33
* Make boost composable Currently Boost enables a few components through variants by default, which means that if you want to use only what you need and no more, you have to explicitly disable these variants, leading to concretization errors whenever a second package explicitly needs those components. For instance if package A only needs `+component_a` it might depend on `boost +component_a ~component_b`. And if packge B only needs `+component_b` it might depend on `boost ~component_a +component_b`. If package C now depends on both A and B, this leads to unsatisfiable variants and hence a concretization error. However, if we default to disabling all components, package A can simply depend on `boost +component_a` and package B on `boost +component_b` and package C will concretize to depending on `boost +component_a +component_b`, and whatever you install, you get the bare minimum. * Fix style * Added composable boost dependencies for folly * fixing akantu merge issue * hpctoolkit boost dependencies already defined * Fix Styles * Fixup style once more * Adding isort fix * isort one more time * Fix for package audit issue Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com> Co-authored-by: Ryan O'Malley <rd.omalley@comcast.net>
2022-03-04boost: update version analysis patch for fujitsu compiler. (#29198)Toyohisa Kameyama2-1/+13
2022-01-17Fixing pthread-stack-min-fix.patch patch version range (#28437)Vanessasaurus1-2/+2
pthread-stack-min-fix.patch should no be applied to 1.73.0 See https://github.com/spack/spack/issues/28436
2022-01-15Fix boost build failures on newer glibcPeter Brady2-0/+19
2022-01-14Update copyright year to 2022Todd Gamblin1-1/+1
2021-12-09boost: add v1.78 (#27889)eugeneswalker1-0/+1
2021-11-11boost: ensure Spack wrappers are used for %intel (#27348)Tiziano Müller1-8/+10
Fixes #26117
2021-10-12boost: Fix build of 1.53:1.54 with glibc>=2.17 (#26659)Bernhard Kaindl1-0/+4
Fix missing declaration of uintptr_t with glibc>=2.17 in 1.53:1.54 See: https://bugs.gentoo.org/482372
2021-10-03Remove .99 from version ranges (#26422)Harmen Stoppels1-13/+13
In most cases, .99 can be omitted thanks to #26402 .
2021-10-01boost: @1.77.0: need updated python_jam.patch for +python (#26363)bernhardkaindl2-2/+45
One hunk changed and the new patch is refreshed using quilt.
2021-09-21boost: fix for @1.77.0%intel (#25965)Tiziano Müller1-0/+6
Add patch for build script from boost repo.
2021-09-13Switch http to https where latter exists (#25672)Tamara Dahlgren1-3/+3
* Switch http to https where latter exists * Hopefully restore original permissions * Add URL updates after include the -L curl option * Manual corrections to select URL format strings
2021-09-05boost @1.76: set toolset for intel b2 invocation (#25722)Peter Scheibel1-1/+7
and simplify constraint and add explanatory comment
2021-08-30Add patch to fix Boost with CCE and CUDA (#25534)Mikael Simberg1-0/+7
2021-08-30boost: add v1.77.0 (#25536)Mikael Simberg1-0/+1
2021-08-26fixing "problems in speck" as identified by repology (#25491)Vanessasaurus1-1/+1
Most of these are perl packages that need to point to the meta docs site, and then a fair amount of http addresses that need to be https, and then the rest are usually documentation sites that no longer exist or were otherwise changes Signed-off-by: vsoch <vsoch@users.noreply.github.com> Co-authored-by: vsoch <vsoch@users.noreply.github.com>
generated by cgit v1.2.3-60-g2f50 (git 2.42.0) at 2024-06-27 07:24:16 +0000