ci: restore aws-lc-rs crypto provider, use cargo-c for librustls install #5
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.
👋 @icing As promised here's a quick follow-up to #4
The
aws-lc-rs
build issue ended up being specific to the 0.14.1 release. Our oldMakefile
setCFLAGS
globally with fairly aggressive settings for warnings. The intent was to use those settings when building theclient.c
andserver.c
examples, but it was inadvertently being used bycargo
when building native dependencies oflibrustls
, likeaws-lc-sys
.That was causing issues because the
aws-lc-sys
version in use doesn't build cleanly w/ that level of pedantic warnings and so was breaking the build. That's been tided up upstream by the AWS folks inaws-lc
, but for 0.14.1 the easiest thing is to work around this by usingmake CFLAGS="" ... install
in our CI.I also replaced the
cmake
usage with directcargo capi
invocation for simplicity/directness.Thanks again for getting the CI set up! Much appreciated 🙇