Updating freebsd to omit the devcrypto engine which is breaking #1915
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.
In compiling Ruby 3.0.4 out for an updated Chef 17.0.149 build we encountered a couple of issues. First, compilation for openssl was dying and causing the builder to spit this error message out:
if you search on the "eng_cryptodev.c... " in the error output above you get exactly 1 hit from Google which is the patch put out by Freebsd.org that tells you how to fix this: Go Here
The only issue with that patch is that it adds a version constraint limiting devcrypto to Freebsd 13 or less. The workaround for that moving forward is to simply add dev crypto to your modules list and voila!
Description
Related Issue
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.