Add fix for running jazzy on M1/ARM #659
Merged
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
birkskyum
approved these changes
Jan 5, 2023
birkskyum
requested changes
Jan 5, 2023
|
This is pretty much what is installed on the runners now: Ruby might be missing, so just install that too. |
|
The other gem seems to install just fine though (I think ruby is available by default on macOS). Could you give me access so I can check the logs? |
artakka
force-pushed
the
fix-ios-build-m1-jazzy
branch
from
ed60453 to
5c6c1c8
Compare
birkskyum
approved these changes
Jan 6, 2023
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.
Ran into an issue when running the GitHub action for the iOS release: https://github.com/maplibre/maplibre-gl-native/actions/runs/3848364221/jobs/6556050541
It is a known problem that is caused by running jazzy on M1/ARM chip: