Ruby 3.0 is incompatible for building fat gems on Windows:#13
Merged
Edouard-chin merged 1 commit intomainfrom Oct 28, 2025
Merged
Ruby 3.0 is incompatible for building fat gems on Windows:#13Edouard-chin merged 1 commit intomainfrom
Edouard-chin merged 1 commit intomainfrom
Conversation
- This is a windows specific issue. I'm modifying this for all platforms to make things simple but ultimately this should be a windows only solution. The problem being that on Ruby 3.0, the C-runtime is different than on 3.1+. So when 3.0 gets picked up for compiling the extensions for all others versions, we end up with broken binaries.
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
1 participant
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.
This is a windows specific issue. I'm modifying this for all platforms to make things simple but ultimately this should be a windows only solution. Though Ruby 3.0 is so old I don't know if it make sense to put a lot of effort into it.
The problem being that on Ruby 3.0 for windows, the C-runtime is different than on 3.1+. So when 3.0 gets picked up for compiling the extensions for all others versions, we end up with broken binaries.