Closed Luni-4 closed 1 year ago
It seems we have to change the musl
target into the gnu
one due to this error: https://github.com/sifis-home/sifis-generate/actions/runs/4183591092/jobs/7248563008#step:6:86
It seems we have to change the
musl
target into thegnu
one due to this error: https://github.com/sifis-home/sifis-generate/actions/runs/4183591092/jobs/7248563008#step:6:86
That is due to compiling the fuzz target with musl
in that project; it shouldn't matter whether cargo fuzz
itself is musl
or not since the cargo fuzz
binary does not include libFuzzer
.
That is, we should not change away from musl
for these deploy actions.
It seems we have to change the
musl
target into thegnu
one due to this error: https://github.com/sifis-home/sifis-generate/actions/runs/4183591092/jobs/7248563008#step:6:86That is due to compiling the fuzz target with
musl
in that project; it shouldn't matter whethercargo fuzz
itself ismusl
or not since thecargo fuzz
binary does not includelibFuzzer
.
I haven't installed any musl
library in that project, just cargo-fuzz
which has been built with musl
. I suppose this problem could happen to many others. Is there a workaround for that? Or can I add a gnu
target to the deploy script?
I've tried to install musl
libraries and launch this command cargo fuzz build --target x86_64-unknown-linux-musl
but without any success
@fitzgen I've decided to release a gnu
binary too. What do you think?
I was able to fix my problem setting up the target
cargo fuzz build --target x86_64-unknown-linux-gnu
@fitzgen I rebased the PR, can we merge it now?
This PR improves
deploy
actions simplifying some operations and removing some useless ones