Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was introduced in #8668 but it doesn't appear to be necessary, and its presence breaks wasmtime-cli builds for x86_64-unknown-linux-musl on linux (tested with AWS2023, a redhat derivative) when using the default linker.
CI overrides the linker with a
musl-gcc
install. I'm not sure why, and at least in my project, we build without using the musl-gcc linker and everything works perfectly, and adopting that strategy broke something in a way I couldn't debug. So, I'd like it for CI to test the musl build with the default linker as well, to catch issues like this one. The CI matrix / docker configuration is pretty complicated and I was gonna consult with @alexcrichton on the best way to add this check.