Fix: Explicitly use conda-provided gem binary during install to avoid macOS system Ruby conflicts #6623
Conversation
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
… macOS system Ruby conflicts
…website locally on Macbook.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
On Intel-based MacBooks, the system Ruby (v2.6) often takes precedence in the PATH even after environment activation, causing make install to fail because rubygems-update requires Ruby >= 3.2.0. This change explicitly points to the gem binary within the Conda prefix to ensure the correct version is used.
Tested and works on a computer with the following info:
To build the website locally, I also had to provide
make serve-quick HOST=127.0.0.1instead of the default0.0.0.0. Added this information torendering_gtnfile.