You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried running honggfuzz with both the original make that comes with OSX (3.81) and with one installed via homebrew (4.3) - in both cases I get this error:
❯ cargo hfuzz run try-hong
Compiling honggfuzz v0.5.54
Compiling arbitrary v1.0.1
Compiling lazy_static v1.4.0
error: failed to run custom build command for `honggfuzz v0.5.54`
Caused by:
process didn't exit successfully: `/Users/ilmoi/Downloads/try-hong/hfuzz_target/release/build/honggfuzz-f99475d7c12e0151/build-script-build` (exit code: 101)
--- stdout
make: Entering directory '/Users/ilmoi/.cargo/registry/src/github.com-1ecc6299db9ec823/honggfuzz-0.5.54/honggfuzz'
make: Leaving directory '/Users/ilmoi/.cargo/registry/src/github.com-1ecc6299db9ec823/honggfuzz-0.5.54/honggfuzz'
--- stderr
Makefile:103: *** Unsupported MAC OS X version. Stop.
thread 'main' panicked at 'assertion failed: status.success()', /Users/ilmoi/.cargo/registry/src/github.com-1ecc6299db9ec823/honggfuzz-0.5.54/build.rs:41:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
The advice here didn't help and I'm not finding anything useful on google.
Is there anything else I can try and do?
I'm on Big Sur 11.4
The text was updated successfully, but these errors were encountered:
In the meantime, I would recommend you to use some Linux to do your fuzzing. Compatibility, features and support is almost always better for this kind of projects.
@PaulGrandperrin@ilmoi Just had the same issue with MacOs. I believe google/honggfuzz#371 was closed successfully some time ago.
However, mentioned lines in Makefile are still there...
I've tried running
honggfuzz
with both the original make that comes with OSX (3.81) and with one installed via homebrew (4.3) - in both cases I get this error:The advice here didn't help and I'm not finding anything useful on google.
Is there anything else I can try and do?
I'm on Big Sur 11.4
The text was updated successfully, but these errors were encountered: