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

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

Open
sylann opened this issue Oct 2, 2024 · 0 comments

Comments

@sylann
Copy link

sylann commented Oct 2, 2024

Similar issues:

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.

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