Error running libafl_libfuzzer_runtime/build.sh with stable toolchain

[mschwager]

IMPORTANT

1. You have verified that the issue to be present in the current main branch

Thank you for making LibAFL better!

Describe the bug
A clear and concise description of what the bug is.
If you want to present the backtrace, don't forget to run with errors_backtrace feature and log from RUST_LOG
In addition, please tell us what is your fuzzer's Cargo.toml

I'm trying to build the standalone libFuzzer compatibility library by running build.sh. nightly is giving me build errors, so I tried to build with stable and get the following error:

#13 [libafl-builder 7/7] RUN bash build.sh --toolchain stable
#13 84.57     Finished `release` profile [optimized + debuginfo] target(s) in 1m 24s
#13 84.60 error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel
#13 84.60 See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
#13 ERROR: process "/bin/sh -c bash build.sh --toolchain stable" did not complete successfully: exit code: 101

To Reproduce
Steps to reproduce the behavior:

1. bash build.sh --toolchain stable

Expected behavior
A clear and concise description of what you expected to happen.

The library successfully builds against the stable channel.

Screen output/Screenshots
If applicable, add copy-paste of the screen output or screenshot that shows the issue. Please ensure the output is in English and not in Chinese, Russian, German, etc.

Additional context
Add any other context about the problem here.

[domenukk]

I don't think this is possible right now. @addisoncrump would know more

[addisoncrump]

Hm, we rely on nightly right now because of symbolization requirements. What's the build error you get on nightly?

[mschwager]

...
#13 15.47    Compiling libafl_targets v0.16.0 (/libafl/crates/libafl_targets)
...
#13 17.31    Compiling libafl_libfuzzer_runtime v0.16.0 (/libafl/crates/libafl_libfuzzer_runtime)
#13 17.70    Compiling env_logger v0.11.10
#13 17.73    Compiling mimalloc v0.1.48
#13 21.03 error: feature `portable_simd` is declared but not used
#13 21.03  --> /libafl/crates/libafl_targets/src/lib.rs:8:30
#13 21.03   |
#13 21.03 8 | #![cfg_attr(nightly, feature(portable_simd))]
#13 21.03   |                              ^^^^^^^^^^^^^
#13 21.03   |
#13 21.03   = note: `-D unused-features` implied by `-D warnings`
#13 21.03   = help: to override `-D warnings` add `#[allow(unused_features)]`
#13 21.03 
#13 21.75 error: could not compile `libafl_targets` (lib) due to 1 previous error
#13 21.75 warning: build failed, waiting for other jobs to finish...
#13 ERROR: process "/bin/sh -c bash build.sh" did not complete successfully: exit code: 101
------
 > [libafl-builder 7/7] RUN bash build.sh:
21.03  --> /libafl/crates/libafl_targets/src/lib.rs:8:30
21.03   |
21.03 8 | #![cfg_attr(nightly, feature(portable_simd))]
21.03   |                              ^^^^^^^^^^^^^
21.03   |
21.03   = note: `-D unused-features` implied by `-D warnings`
21.03   = help: to override `-D warnings` add `#[allow(unused_features)]`
21.03 
21.75 error: could not compile `libafl_targets` (lib) due to 1 previous error
21.75 warning: build failed, waiting for other jobs to finish...
------
Dockerfile.LibAFL:39
--------------------
  37 |     WORKDIR /libafl/crates/libafl_libfuzzer_runtime
  38 |     
  39 | >>> RUN bash build.sh
  40 |     
  41 |     # Stage 2: Build ruzzy with LibAFL's libFuzzer
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c bash build.sh" did not complete successfully: exit code: 101

A successful build is the priority here, but does it make sense for build.sh to take a --toolchain argument if it requires nightly?

[mannubaveja007]

Hi @mschwager @addisoncrump @domenukk , I reproduced this issue on my Arm64 Machines (MacOS, Linux).

Fixed the portable_simd error that's been preventing Nightly builds

Tested it on Linux (ARM64) and macOS screenshots included in the PR to check

pls check the PR #3773

to check clone this via

git clone -b fix/nightly-lints https://github.com/mannubaveja007/LibAFL.git

[addisoncrump]

This is also already fixed in #3752 ...

[addisoncrump]

@mschwager, just FYI: libafl_libfuzzer will get considerably more stable following the next release, as we're going to split up the monorepo and start pinning libafl_libfuzzer to known-good libafl versions. No more of this "will it actually build from main" nonsense.

[mschwager]

@mschwager, just FYI: libafl_libfuzzer will get considerably more stable following the next release, as we're going to split up the monorepo and start pinning libafl_libfuzzer to known-good libafl versions. No more of this "will it actually build from main" nonsense.

@addisoncrump awesome, thank you for doing that. Might I ask for a quick review on this short PR too: #3734? I'm currently working on adding LibAFL support to Ruzzy and blogging about it, and this PR would help out a lot.