Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove require_llvm implementation #2231

Merged
merged 1 commit into from
Aug 8, 2023
Merged

Remove require_llvm implementation #2231

merged 1 commit into from
Aug 8, 2023

Conversation

mislav
Copy link
Member

@mislav mislav commented Aug 3, 2023

This was used by Rubinius over the years to ensure that a correct LLVM version was selected from the ones available on the system, but for recent Rubinius + LLVM 3.7 this function was a no-op anyway, and since Rubinius isn't an actively maintained project anymore, I don't feel strongly for keeping ruby-build workarounds that only help outdated Rubinius versions.

@brixen: Any concerns?

This was used by Rubinius over the years to ensure that a correct llvm version was selected from the ones available on the system, but for recent Rubinius this function is a no-op, and since Rubinius isn't an actively maintained project anymore, I don't feel strongly for keeping ruby-build workarounds that only help ancient Rubinius versions.
@mislav mislav merged commit 4d4678b into master Aug 8, 2023
6 checks passed
@mislav mislav deleted the llvm-cleanup branch August 8, 2023 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants