This repository has been archived by the owner on Jul 4, 2023. It is now read-only.
macvim: Fix compilation on Mac OS X 10.9 #20473
Closed
felixbuenemann
wants to merge
1
commit into
Homebrew:master
from
felixbuenemann:macvim-fix-mavericks-compile
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this need changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the brew binary still uses ruby 1.8 which RUBY_PATH is derived from, so configure would detect ruby version 1.8 while compiling against the Ruby 2.0 framework, which would fail. This is because it uses
-framework Ruby
to compile, which will choose the Current version, which will be 1.8 on older OS X and 2.0 on 10.9. So using the Current ruby binary just matches the version detection to the Current framework.Another approach would be to adjust configure to compile against the Ruby framework matching the ruby-command but I don't see the value of using an outdated framework.