-
Notifications
You must be signed in to change notification settings - Fork 148
Closed
Labels
status:awaiting user responseWhen awaiting user responseWhen awaiting user responsestatus:staletype:bugBugBug
Description
Description of the bug:
Trying to build it for my linux desktop and I am getting this error.
bazel run -c opt :text_generator_main -- --tflite_model=../../../../../qwen_0_5b_converted_full_q8_ekv256.tflite --sentencepiece_model=/data_nvme1n1/llm-ngp/qwen0_5b.spm.model --stop_token="<|endoftext|>" --num_threads=16 --prompt="Write an email:"
Starting local Bazel server and connecting to it...
DEBUG: /home/harcho01/.cache/bazel/_bazel_harcho01/99426edc1602231826962256fa57e6b9/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/harcho01/.cache/bazel/_bazel_harcho01/99426edc1602231826962256fa57e6b9/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'XNNPACK' because it already exists.
ERROR: /data_nvme1n1/llm-ngp/ai-edge-torch/WORKSPACE:110:23: fetching android_ndk_repository rule //external:androidndk: Either the path attribute of android_ndk_repository or the ANDROID_NDK_HOME environment variable must be set.
ERROR: Analysis of target '//ai_edge_torch/generative/examples/cpp:text_generator_main' failed; build aborted: Either the path attribute of android_ndk_repository or the ANDROID_NDK_HOME environment variable must be set.
INFO: Elapsed time: 2.938s
INFO: 0 processes.
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully (6 packages loaded, 9 targets conf\
igured)
currently loading: @bazel_tools//tools/jdk ... (3 packages)
Fetching repository @local_jdk; starting
Fetching repository @local_config_sh; starting
Fetching repository @remotejdk11_macos_toolchain_config_repo; starting
Fetching ...itory @remotejdk11_linux_s390x_toolchain_config_repo; starting
Fetching ...ory @remotejdk11_linux_aarch64_toolchain_config_repo; starting
Fetching repository @remotejdk11_linux_toolchain_config_repo; starting
Fetching repository @remotejdk11_win_toolchain_config_repo; starting
Fetching ...tejdk17_linux_toolchain_config_repo; starting ... (22 fetches)
Actual vs expected behavior:
No response
Any other information you'd like to share?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
status:awaiting user responseWhen awaiting user responseWhen awaiting user responsestatus:staletype:bugBugBug