Skip to content


Cleanup various building/packaging problems #2915

YorickPeterse opened this Issue · 3 comments

1 participant


This is more of a universal ticket to keep track of a few issues I'm currently bumping into when trying to build a Rubinius binary (in particular for Amazon CentOS).

Currently the following problems are present:

  • Trying to run rake package:binary will result in an error of Rake not being found. This seems to be caused by the resetting of GEM_HOME / GEM_PATH.
  • Removing the above will result in an error about Gem::UserInteraction not being found.
  • When running ./configure the warning /home/yorickpeterse/.rubies/ruby-2.1.0/bin/ruby: No such file or directory -- clean (LoadError) pops up.

I'm keeping these in a single issue for the time being since they're most likely related to each other.


As an extra note, the above issues occur both on my local Arch Linux development environment as well as on our production Amazon CentOS servers. They occur either when building from Git or from a Tar archive (e.g. the one of 2.2.4).

Git commit 18b26ab was a late night attempt it fixing some of the above but I reverted it due to it breaking a few other things.


Observation regarding the Gem constant error, it seems Rubinius thinks that the corresponding file (rubygems/user_interaction) is already loaded when this is not the case. The require() call returns false but the constant it should define isn't there yet. Interesting enough GEM_PATH and GEM_HOME are reset in the Rake task that calls this code. This suggests that they need to be at an earlier point.

@YorickPeterse YorickPeterse closed this issue from a commit
@YorickPeterse YorickPeterse Detect tools before cleaning in ./configure
Previously this script would first try to run `ruby -S rake clean`. The `rake`
command here was pulled from the `@rake` instance variable. Due to this
variable not being set by default at this point the resulting command would be
`ruby -S clean` instead, resulting in a load error.

This commit fixes this by first checking the tools used and *then* running a

This fixes #2915.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.