-
Notifications
You must be signed in to change notification settings - Fork 17
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
devcontainer tensorflow build problem when running container on ARM64 #35
Comments
I followed tensorflow instruction and created a script to install bazel on arm machines. However, I'm getting an error when doing the install. Filed a bug with bazel. Here is the script that does the bazel install in case it could be helpful.
|
@juliays I am not sure whether you already had a look at it but, in this issue, someone figured out how to make this work on M1 and posted a gist |
Not core chariott functionality but needed to run dogmode app. Needs more investigation into dependencies. Needs MacOS community user to help. #helpwanted #backlog |
I got the exact same error in my ec2 instance with arm64 architecture. I am not sure whether the solution that I have used will work for Mac with M1 chip, but it worked for me (I am using ec2 instance of arm64 architecture running Debian 12) Install bazelisk (A user friendly launcher for bazel) Change the downloaded file as an executable Please note that the commands given above are used by me in my machine. I haven't used Mac before, so please change it accordingly for your machines and architectures. The reference links are: I hope this helps. |
"cargo build --workspace" failed after starting devcontainer on Macbook with M1 chip.
Expected Behavior
Apps defined in cargo.toml [workspace] section should build
Current Behavior
Error when building tensorflow-sys. Error message is copied below -
vscode ➜ /workspaces/chariott (main ✗) $ cargo build --workspace
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on build directory
Compiling tensorflow-sys v0.22.1
Compiling mock-vas v0.1.0 (/workspaces/chariott/examples/applications/mock-vas)
Compiling kv-app v0.1.0 (/workspaces/chariott/examples/applications/kv-app)
Compiling cloud-object-detection-app v0.1.0 (/workspaces/chariott/examples/applications/cloud-object-detection)
Compiling chariott v0.1.0 (/workspaces/chariott)
Compiling lt-provider-app v0.1.0 (/workspaces/chariott/examples/applications/lt-provider)
error: failed to run custom build command for
tensorflow-sys v0.22.1
Caused by:
process didn't exit successfully:
/workspaces/chariott/target/debug/build/tensorflow-sys-6b5908438712dc75/build-script-build
(exit status: 1)--- stdout
cargo:rerun-if-env-changed=TENSORFLOW_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=TENSORFLOW_STATIC
cargo:rerun-if-env-changed=TENSORFLOW_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
tensorflow-sys/build.rs:309: output = "/workspaces/chariott/target/debug/build/tensorflow-sys-090d29f4eb498d4e/out"
tensorflow-sys/build.rs:311: source = "/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/tensorflow-sys-0.22.1/target/source-v2.9.1"
tensorflow-sys/build.rs:313: lib_dir = "/workspaces/chariott/target/debug/build/tensorflow-sys-090d29f4eb498d4e/out/lib-v2.9.1"
tensorflow-sys/build.rs:315: Directory "/workspaces/chariott/target/debug/build/tensorflow-sys-090d29f4eb498d4e/out/lib-v2.9.1" already exists
tensorflow-sys/build.rs:322: framework_library_path = "/workspaces/chariott/target/debug/build/tensorflow-sys-090d29f4eb498d4e/out/lib-v2.9.1/libtensorflow_framework.so.2"
tensorflow-sys/build.rs:325: library_path = "/workspaces/chariott/target/debug/build/tensorflow-sys-090d29f4eb498d4e/out/lib-v2.9.1/libtensorflow.so.2"
tensorflow-sys/build.rs:442: Executing "bazel" "version"
cargo:error=Bazel must be installed at version 3.7.2 or greater. (Error: No such file or directory (os error 2))
warning: build failed, waiting for other jobs to finish...
error: linking with
cc
failed: exit status: 1Steps to Reproduce
Context (Environment)
tensorflow crate needs to be rebuilt on non x86-64 linux or Mac
Logs
Additional Information
The text was updated successfully, but these errors were encountered: