Open sgammon opened 3 years ago
@dgcoffman i saw you applied the changes that introduced Bazel 4 compatibility. we're on 4.0 and getting this error -- any ideas?
Not really... the error message looks to me like it's being generated from a failure in the error handling code itself, so who knows what the actual failure was
def _exec(repository_ctx, command):
if repository_ctx.attr.trace:
print("__EXEC", command)
output = repository_ctx.execute(command)
if output.return_code != 0:
print("__OUTPUT", output.return_code, output.stdout, output.stderr)
fail("Could not exec command " + " ".join(command))
elif repository_ctx.attr.trace:
print("__OUTPUT", output.return_code, output.stdout, output.stderr)
return output
The examples in this codebase are a good test harness, so if you want to go deep, you can attempt to replicate the failure in one of the examples and then you can debug workspace.bzl.
While trying to build an iOS application linked to some pods (non-vendored), I get the following error:
I figured this might be an incompatibility with Bazel 4.0.0, which we recently switched to. I saw the recent commits on
master
related to Bazel 4 compatibility, but when usingmaster
directly, I run into #112.WORKSPACE
: