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

upgrade from 0.5.52 to 0.5.53 breaks #48

Closed
drahnr opened this issue Mar 3, 2021 · 3 comments · Fixed by #49
Closed

upgrade from 0.5.52 to 0.5.53 breaks #48

drahnr opened this issue Mar 3, 2021 · 3 comments · Fixed by #49

Comments

@drahnr
Copy link
Contributor

drahnr commented Mar 3, 2021

error: failed to run custom build command for `honggfuzz v0.5.53`

Caused by:
  process didn't exit successfully: `/media/supersonic1t/projects/parity/rsc-perf/fuzzit/hfuzz_target/release/build/honggfuzz-e79e9d36b487ef79/build-script-build` (exit code: 1)
  --- stderr
  honggfuzz dependency (0.5.53) and build command (0.5.52) versions do not match

happens since the update in Cargo.toml.

@drahnr
Copy link
Contributor Author

drahnr commented Mar 3, 2021

The git version with the same content works though

@drahnr
Copy link
Contributor Author

drahnr commented Mar 3, 2021

The error message from build.rs should just be better I guess:

eprintln!("honggfuzz dependency ({}) and build command ({}) versions do not match",
                  VERSION, honggfuzz_build_version);

is not clear in what should be done to resolve the issue.

I'll create a PR to improve the msg soon.

@PaulGrandperrin
Copy link
Member

PaulGrandperrin commented Mar 3, 2021

I guess you just need to cargo install honggfuzz again, so that your local binary matches the library dependency.
I agree, the message could be better.
Just adding a something like
please adjust your Cargo.toml to "honggfuzz = \"{0}\"" or run "cargo install honggfuzz --version \"{1}\""
would be nice

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.

2 participants