axiom-configure broken for ARM architecture. #802
Conversation
This file contains 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
…rrect ones on arm arch
…rrect ones on arm arch
…rrect ones on arm arch
sho-luv
changed the title
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.
If you run the configure command on a Arm system the auto configure over writes the ARM binaries with AMD64 ones. This breaks what was previously working. I added checks to at a minimum not break existing binaries. I could change the code to locate the binaires of arm if detected. But I'm not sure thats what you wanted. As it stands it just breaks your system if you are on ARM. So I just at a min had it check if the bins already existed before trying to install them again.