-
Notifications
You must be signed in to change notification settings - Fork 1
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
Backend build failure #16
Comments
The above includes the command line output resulting from cargo test - here is the (nearly identical) output from cargo run: C:\Users\adity\Documents\CSE 403\FitSocial\backend>cargo run Caused by: --- stderr |
DelSkayn/rquickjs#88 take a look at this. It might be the same issue. |
I'm getting a similar error (with the same steps to reproduce) when running
|
Looks like you need to install libclang (I think clang from your package manager) |
I got it working, thank you! I switched to Windows (64-bit) since I had some issues installing clang on attu (independent of this project). There, I installed clang, and ran |
Description
Backend fails to build after following the instructions in the readme.
To Reproduce
I followed the instructions as written in the readme.
Expected behavior
The backend starts up.
Actual behavior
The build failed with the following output:
C:\Users\adity\Documents\CSE 403\FitSocial\backend>cargo test
Compiling async-io v1.12.0
Compiling rquickjs-sys v0.1.7
Compiling devise_core v0.2.1
Compiling kv-log-macro v1.0.7
Compiling log v0.3.9
Compiling aead v0.5.1
Compiling rand_chacha v0.3.1
Compiling ref-cast-impl v1.0.14
Compiling spinning_top v0.2.5
Compiling hash32 v0.2.1
Compiling schannel v0.1.21
Compiling socket2 v0.4.7
Compiling windows-sys v0.42.0
Compiling proc-macro-error v1.0.4
Compiling uncased v0.9.7
error: failed to run custom build command for
rquickjs-sys v0.1.7
Caused by:
process didn't exit successfully:
C:\Users\adity\Documents\CSE 403\FitSocial\backend\target\debug\build\rquickjs-sys-fbb25584092fe374\build-script-build
(exit code: 101)--- stdout
cargo:rerun-if-changed=build.rs
cargo:rerun-if-env-changed=CARGO_FEATURE_EXPORTS
cargo:rerun-if-env-changed=CARGO_FEATURE_BINDGEN
cargo:rerun-if-env-changed=CARGO_FEATURE_UPDATE_BINDINGS
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_BYTECODE
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_GC
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_GC_FREE
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_FREE
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_LEAKS
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_MEM
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_OBJECTS
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_ATOMS
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_SHAPES
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_MODULE_RESOLVE
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_PROMISE
cargo:rerun-if-env-changed=CARGO_FEATURE_DUMP_READ_OBJECT
--- stderr
thread 'main' panicked at 'called
Result::unwrap()
on anErr
value: Error { kind: NotFound, message: "program not found" }', C:\Users\adity.cargo\registry\src\github.51.al-1ecc6299db9ec823\rquickjs-sys-0.1.7\build.rs:136:10note: run with
RUST_BACKTRACE=1
environment variable to display a backtracewarning: build failed, waiting for other jobs to finish...
Additional context
I'm using a 64-bit Windows PC.
The text was updated successfully, but these errors were encountered: