/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/Rakefile requires "ruby" to be in the PATH

[FooBarWidget]

From will.vande on May 21, 2008 02:44:23

What steps will reproduce the problem? 1. install ruby binary with alternative name eg. ruby1.8
2. gem install passenger
3. passenger-install-apache2-module What is the expected output? What do you see instead? Expected : The Apache 2 module was successfully installed
Got:

In ext/passenger:

ruby extconf.rb
rake aborted!
Command failed with status (127): [ruby extconf.rb...]
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/Rakefile:67
(See full trace by running task with --trace)

---

It looks like something went wrong What version of the product are you using? On what operating system? passenger-1.0.5
rubygems 1.1.1
ruby 1.8.5
debian etch

Please provide any additional information below:

installing ruby1.8 in debian etch installs the binary ruby1.8.

Passenger correctly identitfies the correct ruby install when it generates
the config file:

RailsRuby /usr/bin/ruby1.8

So why not use the correct binary in the rake task?

For me install passenger was easy. I edited
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.5/Rakefile and modified line 67 from

sh "ruby extconf.rb"

to

sh "ruby1.8 extconf.rb"

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=69

[FooBarWidget]

From will.vande on May 20, 2008 17:54:25

Using the RUBY constant seems to fix the problem. Patch/diff attached.

Attachment: Rakefile.patch

[FooBarWidget]

From honglilai on May 21, 2008 05:01:43

Thanks, the patch has been applied.

Status: Fixed
Labels: Milestone-1.1.0

[FooBarWidget]

From honglilai on June 11, 2008 00:32:32

Labels: -Milestone-1.1.0 Milestone-1.9.0