Skip to content

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

@sylann

Description

@sylann

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions