cloudflare / cloudflare/boring

failed to run custom build command for `boring-sys v4.10.2` (Windows 11 WSL2 arch linux)

Open
#283 19 comments 3 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
522
Forks
171
PR merge metrics
No merged PRs in 30d

Description

Similar issues:
- https://github.com/cloudflare/boring/issues/242
- https://github.com/cloudflare/boring/issues/121

The output:

```
cargo run
Compiling boring-sys v4.10.2
error: failed to run custom build command for `boring-sys v4.10.2`

Caused by:
process didn't exit successfully: `/home/***/***/target/debug/build/boring-sys-21189a854ea148ad/build-script-main` (exit status: 101)
--- stdout

... building logs ...

--- stderr

thread 'main' panicked at /home/***/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bindgen-0.70.1/lib.rs:622:27:
Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

This line seems odd:
> "where one of these files can be found (invalid: [])"

**System information**:
- The computer is a Windows 11 Pro.
- The build is executed on WSL2 (Arch Linux, variant of my company).

I don't install boring-sys directly, it is an indirect dependency of jwt-simple.
```
jwt-simple v0.12.10
├── boring v4.10.2
├── boring-sys v4.10.2
```

Final note, the project builds without any issue on MacOS Sonoma.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.