Fix dnf installation, allow passing in CPU flag#65
Merged
DBezemer merged 3 commits intoDBezemer:devfrom Apr 16, 2024
Merged
Conversation
Owner
|
I would prefer not to add --allowerasing to DNF as this is a package issue on AL2023 and they should solve that themselves |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NO_SUDO=1 makeon systems withdnf(like Amazon Linux 2023), running commandyum install -y curlmight result in the following error:Fix this issue by checking for
dnfbinary and pass in--allowerasingwhen it is detectedCPUflag for buildinghaproxy, and defaults it togenerichaproxywithCPU=armv81"improves HAProxy performance by 4x": https://github.com/aws/aws-graviton-getting-started#recent-software-updates-relevant-to-graviton