-
Notifications
You must be signed in to change notification settings - Fork 74.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: no such file or directory: 'v2' when Bazel build for macOS #69786
Comments
Hi @dingjieliu ,
Thank you! |
Hi Venkat @Venkat6871 I have updated the Clang version to 16.0.0 as recommended. Besides, I run the commend with:
I met an error said no toolchain is configured. (detailed info will be post later) So I modify .bazelrc file by changing build:tf_fuzztest --action_env=CC=/usr/local/bin/clang and build:tf_fuzztest --action_env=CXX=/usr/local/bin/clang++ but the error remaines:
How should I do to set the toolchain configs? Thanks for your help!! |
I just found the Chinese and English pages are different significantly. I will try later. Thanks! |
Hi @dingjieliu ,
Thank you! |
Hi @Venkat6871 , I have updated my clang to 16.0.0
Then I run Bazel to build:
it says:
How should I do? Is it caused by wrong protobuf version or failed download or something else? Does it have some version requirement for protobuf? Thank you! |
tried with v2.12.1 and the error remains. |
Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.13.1
Custom code
No
OS platform and distribution
macOS 14.3.1
Mobile device
no
Python version
3.9
Bazel version
5.3.0
GCC/compiler version
Apple clang version 15.0.0 (clang-1500.1.0.2.5)
CUDA/cuDNN version
np
GPU model and memory
no
Current behavior?
Hi, I am trying to install TensorFlow C lib with Bazel as recommended.
I run:
git clone
git checkout v2.13.1
bazel build --config opt //tensorflow/tools/lib_package:libtensorflow
it says:
Standalone code to reproduce the issue
Relevant log output
The text was updated successfully, but these errors were encountered: