ERROR: No toolchain found for cpu 'k8'.
See original GitHub issuebuchgr@buchgr0:~/Code$ git clone git@github.com:bazelbuild/bazel.git
Cloning into 'bazel'...
Enter passphrase for key '/usr/local/google/home/buchgr/.ssh/id_rsa':
remote: Counting objects: 186522, done.
remote: Compressing objects: 100% (307/307), done.
remote: Total 186522 (delta 219), reused 483 (delta 207), pack-reused 185894
Receiving objects: 100% (186522/186522), 365.36 MiB | 19.85 MiB/s, done.
Resolving deltas: 100% (114132/114132), done.
buchgr@buchgr0:~/Code$ cd bazel
buchgr@buchgr0:~/Code/bazel$ bazel version
.
Build label: 0.5.1
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Tue Jun 6 10:34:11 2017 (1496745251)
Build timestamp: 1496745251
Build timestamp as int: 1496745251
buchgr@buchgr0:~/Code/bazel$ bazel build //src:bazel
ERROR: No toolchain found for cpu 'k8'. Valid cpus are: [
piii,
armeabi-v7a,
x64_windows_msvc,
x64_windows_msys,
s390x,
ios_x86_64,
].
INFO: Elapsed time: 1.466s
buchgr@buchgr0:~/Code/bazel$ bazel clean --expunge
INFO: Starting clean (this may take a while). Consider using --expunge_async if the clean takes more than several minutes.
buchgr@buchgr0:~/Code/bazel$ bazel build //src:bazel
...........
ERROR: No toolchain found for cpu 'k8'. Valid cpus are: [
piii,
armeabi-v7a,
x64_windows_msvc,
x64_windows_msys,
s390x,
ios_x86_64,
].
INFO: Elapsed time: 1.683s
buchgr@buchgr0:~/Code/bazel$ bazel clean
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
buchgr@buchgr0:~/Code/bazel$ bazel shutdown
buchgr@buchgr0:~/Code/bazel$ bazel clean --expunge
...........
INFO: Starting clean (this may take a while). Consider using --expunge_async if the clean takes more than several minutes.
buchgr@buchgr0:~/Code/bazel$ bazel build //src:bazel
...........
ERROR: No toolchain found for cpu 'k8'. Valid cpus are: [
piii,
armeabi-v7a,
x64_windows_msvc,
x64_windows_msys,
s390x,
ios_x86_64,
].
INFO: Elapsed time: 1.575s
buchgr@buchgr0:~/Code/bazel$
buchgr@buchgr0:~$ cat .blazerc
common --show_progress_rate_limit=0.2
build --experimental_ui --experimental_ui_actions_shown 7
build --experimental_skyframe_target_pattern_evaluator
build --nostamp
I have first encountered this problem with bazel 0.5.1.
cc: @mhlopko
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Unable to find toolchain - Google Groups
I'm working on upgrading to bazel 0.21.0. It's a monster. On the plus side, rules_go seems to work with our CROSSTOOL out of...
Read more >Configuring CROSSTOOL - Bazel 0.21.0
Bazel throws the following error: No toolchain found for cpu 'asmjs'. Since you have specified --crosstool_top and --cpu in the .bazelrc file, ...
Read more >"No Toolchain found for Target Local" error when using Meson ...
I've noticed project will issue "gcc -v" command after creation and looks for "Target: xxxx" . In my case if xxxx=x86_64-w64-mingw32, no error...
Read more >TF Lite Android: No default_toolchain found for cpu 'arm64-v8a'
The error is due to bazel not supporting arm64, this is supported here is a workaround, the other way will be to just...
Read more >Bazel: site/docs/tutorial/cc-toolchain-config.md | Fossies
It's based on an example C++ project that builds error-free using clang . ... No such package `toolchain`: BUILD file not found on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
After deleting
./cache/bazel/_bazel_$USER/
folders the bug is gone.Using newest tensorflow and newest bazel, it help , the bug is avoid .