Open addisoncrump opened 9 months ago
I have tested all musl binaries (0.11.2-0.12.0), and they all have this issue.
And, this is due to the following code using the target that is used to build cargo-fuzz itself as the default target.
The more correct way here is to get host triple from the output of cargo --version --verbose
, like this.
(Workaround is passing --target x86_64-unknown-linux-gnu
to cargo fuzz
.)
The more correct way here is to get host triple from the output of
cargo --version --verbose
, like this.
However, to provide the fully same behavior as the default target selection in cargo, a library such as cargo-config2 is needed because we need to handle config while handling its hierarchical structure and environment variables.
Filed #365 to fix this.
Bump, this just happened again.
See: https://github.com/astral-sh/ruff/issues/9368
It seems that binstall (which pulls from GitHub since the release) installs the musl copies distributed in the latest release, but the released files can only build musl-targeting fuzzers.
I would expect that the distributed files should be compatible with any toolchain.