You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hitting what look like breakages inside "zlib" when trying to run the bazelisk build command given to build the repo at head:
$ bazelisk clean && bazelisk build --verbose_failures //:compiler_unshaded_deploy.jar
INFO: Analyzed target //:compiler_unshaded_deploy.jar (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /usr/local/google/home/blickly/.cache/bazel/_bazel_blickly/09474313ad65bad59ec9aec61a59c7c6/external/zlib/BUILD.bazel:31:1: undeclared inclusion(s) in rule '@zlib//:zlib':
this rule is missing dependency declarations for the following files included by 'external/zlib/zutil.c':
'/usr/lib/gcc/x86_64-linux-gnu/10/include/stddef.h'
'/usr/lib/gcc/x86_64-linux-gnu/10/include/limits.h'
'/usr/lib/gcc/x86_64-linux-gnu/10/include/syslimits.h'
'/usr/lib/gcc/x86_64-linux-gnu/10/include/stdarg.h'
Target //:compiler_unshaded_deploy.jar failed to build
INFO: Elapsed time: 0.183s, Critical Path: 0.09s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
This looks like an issue in a dependency, so I'm hoping that this will go away on it's own, but I wanted to check if anyone has seen something like this before? @nreid260, maybe?
The text was updated successfully, but these errors were encountered:
From looking through the bazel issue tracker, it looks very likely to me that this is the same as bazelbuild/bazel#9213, which also gave a "undeclared inclusion(s)" error inside "zlib" on an APT-based linux system after an update.
I'm hitting what look like breakages inside "zlib" when trying to run the
bazelisk build
command given to build the repo at head:This looks like an issue in a dependency, so I'm hoping that this will go away on it's own, but I wanted to check if anyone has seen something like this before? @nreid260, maybe?
The text was updated successfully, but these errors were encountered: