- Nov 15, 2013
-
-
Erik Michaels-Ober authored
-
Erik Michaels-Ober authored
Add definition for jruby-1.7.8
-
Ketan Padegaonkar authored
-
- Nov 14, 2013
-
-
Mislav Marohnić authored
Add a definition for JRuby 1.7.7
-
deepj authored
-
- Nov 13, 2013
-
-
Kelley Reynolds authored
`grep -c` would correctly output "0", which is handled specially later on, but would also exit with a nonzero status which would abort the script. Piping the output to `wc` to do the counting makes the exit status of grep irrelevant. Fixes #447
-
- Oct 30, 2013
-
-
Mislav Marohnić authored
References #443
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
- Oct 29, 2013
-
-
Mislav Marohnić authored
Makes sure that installing Rubinius won't touch other gems outside the build directory.
-
Mislav Marohnić authored
Installing Rubinius would print "BUILD FAILED" at the `bundle` step but the installation would proceed nevertheless and finish successfully. It turns out that the `command ...` expression will trigger the ERR trap on failure even when it's a part of `||` list or a condition inside an `if` statement. This defies how the ERR trap is supposed to work, so the workaround is to execute it in a subshell which doesn't inherit the ERR trap of its parent.
-
Mislav Marohnić authored
This is a regression introduced by d13ae0ad References #267
-
- Oct 28, 2013
-
-
Mislav Marohnić authored
If a commit introduced a new Ruby definition, we want it mirrored even if there might have been an accidental failure on CI.
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
- Oct 27, 2013
-
-
Mislav Marohnić authored
-
-
Mislav Marohnić authored
Fixes #148
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Because OS X Mountain Lion removed X Windows, compiling Ruby 1.8 would fail unless the user installed XQuartz manually and passed: CPPFLAGS=-I/opt/X11/include rbenv install 1.8.7-p374 This auto-detects if `/opt/X11/include` is present on the system and configures CPPFLAGS accordingly. However if XQuartz was never installed, we simply configure Ruby using `--without-tk`. Fixes #193 #207 References 35324692
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Alt. implementation of #401, #434
-
Mislav Marohnić authored
The problem wasn't in quoting as per 0b520617, but in the fact that Ruby trunk added a LDFLAGS checker that aborts if any of the paths listed in it are missing: https://github.com/ruby/ruby/commit/3636f8c0f56ddf15e26e28e7a38e748588fad976 This is probably a bug in Ruby, but for now a simple workaround is to iterate through paths in LDFLAGS and ensure they exist. References #441
-
SHIBATA Hiroshi authored
Stop quoting in LDFLAGS and CPPFLAGS. Ruby trunk chokes on it: https://github.com/ruby/ruby/commit/3636f8c0f56ddf15e26e28e7a38e748588fad976 Closes #441
-
- Oct 26, 2013
-
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Example: export RAKE_STUB_DEBUG=2
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Some Rubies need Rake or Bundler for the installation process. However, since the host Ruby version might not have those gems installed, install them in a temporary GEM_HOME and add their executables to PATH. Fixes #426
-
Mislav Marohnić authored
Rake might not be available on the system, but if there is a Gemfile, assume that it bundles rake.
-
Mislav Marohnić authored
Fixes #440
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Use the `cp -f` flag to force unlinking non-writable files. Closes #384
-
Jeremy Stephens authored
When installing mruby-dev, the cp command doesn't use the force flag. This causes an issue when using a custom build configuration (via MRUBY_CONFIG environment variable) and installing mrbgems from Github, as the pack files in the git repositories are read-only.
-
Mislav Marohnić authored
-
Mislav Marohnić authored
Helps avoid the pitfall where ERR trap has no effect. See 262eb165
-
Mislav Marohnić authored
Previously, if `http get` failed, the `download_tarball` function would still continue since the ERR trap had no effect at that point. Given a script in the form of `{ ... } || return 1`, the expressions that are the part of the first group are not subject to ERR trap since they are non-last in a chain of expressions. However, since we still can't count on the ERR trap taking effect in this phase, better just rewrite the function to manually abort. Fixes #394
-