rust-rocksdb / rust-rocksdb/rust-rocksdb
error: failed to run custom build command for `librocksdb-sys v5.18.3` Windows
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.2k
- Forks
- 874
- PR merge metrics
- No merged PRs in 30d
Description
Compiling librocksdb-sys v5.18.3
Compiling cennznet v0.9.25-beta (C:\Users\charingane\Desktop\cennznet-master)
error: failed to run custom build command for librocksdb-sys v5.18.3
Caused by:
process didn't exit successfully: C:\Users\charingane\Desktop\cennznet-master\target\debug\build\librocksdb-sys-b28aaa0ace6f4e98\build-script-build (exit code: 101)
--- stdout
cargo:rerun-if-changed=build.rs
cargo:rerun-if-changed=rocksdb/
cargo:rerun-if-changed=snappy/
cargo:rerun-if-changed=lz4/
cargo:rerun-if-changed=zstd/
cargo:rerun-if-changed=zlib/
cargo:rerun-if-changed=bzip2/
--- stderr
thread 'main' panicked at 'Unable to find libclang: "couldn't find any valid shared libraries matching: ['clang.dll', 'libclang.dll'], set the LIBCLANG_PATH environment variable to a path where one of these files can be found (invalid: [(C:\Program Files\LLVM\bin\libclang.dll: invalid DLL (64-bit))])"', src\libcore\result.rs:1165:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
warning: build failed, waiting for other jobs to finish...
error: build failed

Please how to fix.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the librocksdb-sys v5.18.3 build script and the reported libclang.dll failure on Windows. Check the LLVM path named in the error and the LIBCLANG_PATH environment variable, then rerun cargo build. Done means the custom build command completes without the libclang panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100