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 bandwhich v0.20.0 #233

Closed
ket000 opened this issue Mar 28, 2022 · 2 comments
Closed

failed to run custom build command for bandwhich v0.20.0 #233

ket000 opened this issue Mar 28, 2022 · 2 comments

Comments

@ket000
Copy link

ket000 commented Mar 28, 2022

Trying to build bandwhich on windows using
cargo install bandwhich

Getting below error.

Caused by:
process didn't exit successfully: C:\Users\xxx~1\AppData\Local\Temp\cargo-install2CUw6c\release\build\bandwhich-e4dc500439890925\build-script-build (exit code: 101)
--- stdout
cargo:rerun-if-changed=build.rs

--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: InvalidArchive("Could not find central directory end")', C:\Users\xxx.cargo\registry\src\gh.neting.cc-1ecc6299db9ec823\bandwhich-0.20.0\build.rs:37:57
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile bandwhich v0.20.0, intermediate artifacts can be found at C:\Users\xxx~1\AppData\Local\Temp\cargo-install2CUw6c

Caused by:
build failed

@ScriptingDad
Copy link

fixing the path to npcap as outlined in #234 does resolve the build. I just ran cargo install bandwhich --offline after modifying the build script and it ran through without this error.

@cyqsimon
Copy link
Collaborator

Fixed in #273. See also #275.

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

Successfully merging a pull request may close this issue.

3 participants