Skip to content
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

rocky linux: libz3.so.4.8: cannot open shared object file #43

Open
JonKohler opened this issue May 24, 2022 · 0 comments
Open

rocky linux: libz3.so.4.8: cannot open shared object file #43

JonKohler opened this issue May 24, 2022 · 0 comments

Comments

@JonKohler
Copy link

I haven't been able to find a distro binary for rocky or rhel8 for libz3, this appears like a hard blocker :(

Can't run server without this

[root@localhost schedviz]# yarn bazel run server -- -- -storage_path="/root/git/traces"
yarn run v1.22.18
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ /root/git/schedviz/node_modules/.bin/bazel run server -- -storage_path=/root/git/traces
INFO: Writing tracer profile to '/root/.cache/bazel/_bazel_root/116cb4b37cb5ae33998452196fe24c90/command.profile.gz'
INFO: Analyzed target //server:server (2 packages loaded, 14 targets configured).
INFO: Found 1 target...
ERROR: /root/.cache/bazel/_bazel_root/116cb4b37cb5ae33998452196fe24c90/external/com_google_protobuf/BUILD:388:1: C++ compilation of rule '@com_google_protobuf//:protoc' failed (Exit 127) clang failed: error executing command external/llvm_toolchain/bin/clang -U_FORTIFY_SOURCE -fstack-protector -fno-omit-frame-pointer -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG ... (remaining 39 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
external/llvm_toolchain/bin/clang: error while loading shared libraries: libz3.so.4.8: cannot open shared object file: No such file or directory
Target //server:server failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 25.514s, Critical Path: 1.53s
INFO: 18 processes: 18 linux-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant