Open chiragramani opened 6 months ago
cc: @meteorcloudy
Our postsubmit is green for release-7.1.0: https://buildkite.com/bazel/bazel-bazel/builds/27092#_
OTHER_ARGS='--macos_minimum_os=10.11 --host_cxxopt='-Wno-deprecated-declarations' --host_cxxopt='-Wno-deprecated-builtins'' bazel build //src:bazel --java_runtime_version=remotejdk_11 $OTHER_ARGS
And I couldn't reproduce the issue with on a Mac machine. This is likely a specific issue in your build environment?
Our postsubmit is green for release-7.1.0: https://buildkite.com/bazel/bazel-bazel/builds/27092#_
OTHER_ARGS='--macos_minimum_os=10.11 --host_cxxopt='-Wno-deprecated-declarations' --host_cxxopt='-Wno-deprecated-builtins'' bazel build //src:bazel --java_runtime_version=remotejdk_11 $OTHER_ARGS
And I couldn't reproduce the issue with on a Mac machine. This is likely a specific issue in your build environment?
Unfortunately, I am able to repro this on a different machine as well. From all the commits on release-7.1.0, looks like it work all well until this commit https://github.com/bazelbuild/bazel/commit/8bb56622e6afd2e9e8c2697d25d6a53b5f742da6.
@Wyverald @meteorcloudy As base version is changed from 6.4 to 7.0.2, do you know what changes are needed to get the right toolchain selected (which was being done when 6.4 was used)?
Okay, so from toolchain debugging, looks like the one from apple_support wasn't selected because the other one was registered first. When I modify MODULE.bazel to mention bazel_dep(name = "apple_support", version = "1.8.1")
at the very first, it all works as expected.
Is there a way to get control of this registration part without modifying MODULE.bazel here?
what do you have in your ~/.bazelrc
, if any? (alternatively, try bazel --bazelrc=/dev/null build <the_rest>
)
what do you have in your env
? (please remember to scrub sensitive info)
what do you have in your
~/.bazelrc
, if any? (alternatively, trybazel --bazelrc=/dev/null build <the_rest>
)what do you have in your
env
? (please remember to scrub sensitive info)
it's all the defaults that are present on the release-7.1.0 branch. I also see the same result with bazel --bazelrc=/dev/null build <the_rest>
.
Maybe you can explicitly specify the toolchain with --extra_toolchains
, it should take priority. The toolchains register by bazel_dep respect a BFS order.
I was facing a similar issue, not sure if it's related:
clang: error: unable to execute command: Segmentation fault: 11
clang: error: linker command failed due to signal (use -v to see invocation)
I've had a brew managed clang installation - removing it (brew uninstall llvm
) and relying on the Apple/Xcode provided clang installation instead resolved the issue for me. May be the same for you?
I'm seeing the same segfaults. I've noticed it only happens for me on -c opt
. fastbuild and dbg options work fine.
I've had a brew managed clang installation - removing it (brew uninstall llvm) and relying on the Apple/Xcode provided clang installation instead resolved the issue for me. May be the same for you?
This does resolve the issue for me too. Very odd though.
Description of the bug:
I can build Bazel from source on macOS on 7.0.2 but I see the following CppLink errors when building release-7.1.0
I also see duplicate artifact versions warning
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
On further investigation, 7.1.0 isn't picking up the Xcode toolchain. On release-7.1.0,
On 7.0.2,
Which operating system are you running Bazel on?
macOS 14.3 (23D56)
What is the output of
bazel info release
?release 7.0.2
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response