This repository has been archived by the owner on Oct 1, 2022. It is now read-only.
Work around Rubinius build script choking on RUBYLIB #10
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.
Rubinius'
./configure
script is has a guard that aborts the build if RUBYLIB environment variable is set. As an unfortunate consequence, anybody using "rbenv-gem-rehash" plugin won't be able to build Rubinius.This works around the issue by not writing to RUBYLIB if the name of the script to be executed is
./configure
. Granted, this might affect more projects than just Rubinius, but this assumes that a script named./configure
won't install any gems that need to be rehashed afterwards.This is a terrible thing to do, but I don't see a cleaner workaround.
Fixes #8. Also see rubinius/rubinius#2659