Description of the problem / feature request:
Since Apple charmingly combines their security and feature updates, it is important to be on the latest released version of their operating system and Xcode command line tools. A recent upstream update seems to have broken the ability to compile bazel.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
- Clone and attempt to build bazel with
bazel build //src:bazel on a fully up to date macOS
Expected outcome: successful compilation
Actual outcome:
Compilation fails with the following error:
external/com_google_absl/absl/functional/function_ref.h:124:16: error: definition of implicit copy constructor for 'FunctionRef<void (absl::string_view)>' is deprecated because it has a user-declared copy assignment operator [-Werror,-Wdeprecated-copy]
FunctionRef& operator=(const FunctionRef& rhs) = delete;
^
What operating system are you running Bazel on?
macOS 12.3.1 on an M1 MacBook Air
Command Line Tools for Xcode 13.2
% gcc --version
Apple clang version 13.1.6 (clang-1316.0.21.2)
Target: arm64-apple-darwin21.4.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
What's the output of bazel info release?
% bazel info release
release 5.1.0
What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
[email protected]:bazelbuild/bazel.git
436d04d
436d04d
The same problem manifests when checking out version 5.1.0, 93677c6
Have you found anything relevant by searching the web?
It seems there was a fix landed upstream that is referenced here abseil/abseil-cpp#948
It seems from the commit closing the issue that there is a straight forward one line fix, but it is unclear to me how to patch this in the bazel code base.
When I update the grpc version referenced in distdir_deps.bzl from v1.41.1 to v1.45.1, I can no longer reproduce this problem.
Description of the problem / feature request:
Since Apple charmingly combines their security and feature updates, it is important to be on the latest released version of their operating system and Xcode command line tools. A recent upstream update seems to have broken the ability to compile bazel.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel build //src:bazelon a fully up to date macOSExpected outcome: successful compilation
Actual outcome:
Compilation fails with the following error:
What operating system are you running Bazel on?
macOS 12.3.1 on an M1 MacBook Air
Command Line Tools for Xcode 13.2
What's the output of
bazel info release?What's the output of
git remote get-url origin ; git rev-parse master ; git rev-parse HEAD?git remote get-url origin ; git rev-parse master ; git rev-parse HEAD
[email protected]:bazelbuild/bazel.git
436d04d
436d04d
The same problem manifests when checking out version 5.1.0, 93677c6
Have you found anything relevant by searching the web?
It seems there was a fix landed upstream that is referenced here abseil/abseil-cpp#948
It seems from the commit closing the issue that there is a straight forward one line fix, but it is unclear to me how to patch this in the bazel code base.
When I update the grpc version referenced in
distdir_deps.bzlfrom v1.41.1 to v1.45.1, I can no longer reproduce this problem.