zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bazel patch specs were too restrictive (#40084)

Browse Source 
These patches should always be applied - the existing Bazel code is always wrong, working on some older compilers was a lucky fluke.
This commit is contained in:
Thomas Dickerson 2023-09-21 06:27:11 -04:00 committed by GitHub
parent bd8d0324a9
commit 5d331d4141
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
var/spack/repos/builtin/packages/bazel/package.py
View File

@ -479,13 +479,14 @@ class Bazel(Package):
# https://blog.bazel.build/2021/05/21/bazel-4-1.html
conflicts("platform=darwin target=aarch64:", when="@:4.0")
# patches for compiling bazel-4.1:4 with gcc-11
# patches for compiling various older bazels which had ICWYU
# violations revealed by (but not unique to) GCC 11 header changes.
# these are derived from
# https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/29084/
patch("gcc11_1.patch", when="@0.3.2:4%gcc@11:")
patch("gcc11_2.patch", when="@0.3.2:4%gcc@11:")
patch("gcc11_3.patch", when="@0.3:4%gcc@11:")
patch("gcc11_4.patch", when="@4.1:4%gcc@11:")
patch("gcc11_1.patch", when="@0.3.2:4")
patch("gcc11_2.patch", when="@0.3.2:4")
patch("gcc11_3.patch", when="@0.3:4")
patch("gcc11_4.patch", when="@4.1:4")
# bazel-4.0.0 does not compile with gcc-11
# newer versions of grpc and abseil dependencies are needed but are not in