> ruby 1.8.0 installs its libraries in a different place... so just to be
> sure, try
>      puts RUBY_VERSION
> in your mod_ruby application and see what it reports.

I've reduced the test case to this:

singleton.rbx:

require "singleton"

That doesn't work (same complaining about trying to import the same 
class twice). This does, though:

require "/usr/local/lib/ruby/1.6/singleton.rb"

But "puts RUBY_VERSION" from a .rbx gives me 1.8.0, so it must be 
running from the newest version. But mod_ruby is obviously still using 
the 1.6 singleton.rb file. I just can't figure out why.


/ David