Open inmcm opened 11 months ago
Seems potentially related to recent thread in the Bazel getstarted slack: https://bazelbuild.slack.com/archives/CD42R4HJL/p1702485704389129. If it's the same issue, then you could try using Bazel 6.4, or specifying the --noincompatible_sandbox_hermetic_tmp
build option with 7.0.0; both of these were successful workarounds for me.
I got the same problem,I dig somehow,find it seems the external/gcc_toolchain_x86_64/bin/gcc script parse the EXECROOT not correct,it goes to /tmp,but it seems you need to take bazel-working-directory/_main as your EXECROOT the dir/libs all you need is all here I am new to use bazel, not sure
Can this option be made default or can this be mentioned in the cpp tutorial https://bazel.build/start/cpp
This issue is a significant impediment to new users trying to use the cpp-tutorial to learn bazel. That workflow is completely broken on Ubuntu 20.04 and openSUSE Leap 15.5. I spent two full days finding this issue, mostly because I assumed I was doing something wrong.
Trying to run the cpp-tutorial as written on amd64 Ubuntu 22.04, the compilation process cannot find the external toolchain.
Re-running with verbose flags enabled:
Checking out commit 996a864ab8fb920fc5db7287d342fe16c090b481 (the commit prior to https://github.com/bazelbuild/examples/pull/355 ) and the build works fine with my internal toolchain
Running bazel version 7.0.0 (via bazelisk)
Running on Ubuntu 22.04