Switch back to using custom LLVM builds on CI

[silwol]

Closes: #2921

Description

Switch back to using the custom LLVM builds from wasmerio/llvm-custom-builds.

This will remove the dependency of binaries to libtinfo5, verified that in a VM.

Review

• Add a short description of the change to the CHANGELOG.md file

[epilys]

This seems to result in only linux-amd64 and macos-amd64 using the llvm build (you can see that by going to the make build-wasmer step and see what compiler feature flags it ends up using

https://github.com/wasmerio/wasmer/actions/runs/2493814170

[epilys]

Also, on the llvm builds repository the new build artifacts aren't uploaded as Releases, hence the urls used here are from November 2021

[silwol]

Also, on the llvm builds repository the new build artifacts aren't uploaded as Releases, hence the urls used here are from November 2021

The release tag is from November 2021, but that only contained the source tarballs. The change in Adjust CI for reactivation of custom llvm builds built the releases and attached the artifacts to the release tag, see llvm-custom-builds release 13.x.

[epilys]

The release tag is from November 2021, but that only contained the source tarballs. The change in Adjust CI for reactivation of custom llvm builds built the releases and attached the artifacts to the release tag, see llvm-custom-builds release 13.x.

Oh you're right, missed the upload dates.

[silwol]

This seems to result in only linux-amd64 and macos-amd64 using the llvm build (you can see that by going to the make build-wasmer step and see what compiler feature flags it ends up using

Looking into that…

[epilys]

bors r+

[bors]

Build succeeded:

• Code lint